scholarly journals Enhancing Client Honeypots with Grid Services and Workflows

2021 ◽  
Author(s):  
◽  
David Stirling

<p>Client honeypots are devices for detecting malicious servers on a network. They interact with potentially malicious servers and analyse the Web pages returned to assess whether these pages contain an attack. This type of attack is termed a 'drive-by-download'. Low-interaction client honeypots operate a signature-based approach to detecting known malicious code. High- interaction client honeypots run client applications in full operating systems that are usually hosted by a virtual machine. The operating systems are either internally or externally monitored for anomalous behaviour. In recent years there have been a growing number of client honeypot systems being developed, but there is little interoperability between systems because each has its own custom operational scripts and data formats. By creating interoperability through standard interfaces we could more easily share usage of client honeypots and the data collected. Another problem is providing a simple means of managing an installation of client honeypots. Work ows are a popular technology for allowing end-users to co-ordinate e-science experiments, so these work ow systems can potentially be utilised for client honeypot management. To formulate requirements for management we ran moderate-scale scans of the .nz domain over several months using a manual script-based approach. The main requirements were a system that is user-oriented, loosely-coupled, and integrated with Grid computing|allowing for resource sharing across organisations. Our system design uses Grid services (extensions to Web services) to wrap client honeypots, a manager component acts as a broker for user access, and workflows orchestrate the Grid services. Our prototype wraps our case study - Capture-HPC -with these services, using the Taverna workflow system, and a Web portal for user access. When evaluating our experiences we found that while our system design met our requirements, currently a Java-based application operating on our Web services provides some advantages over our Taverna approach - particularly for modifying workflows, maintainability, and dealing with  failure. The Taverna workflows, however, are better suited for the data analysis phase and have some usability advantages. Workflow languages such as Taverna are still relatively immature, so improvements are likely to be made. Both of these approaches are significantly easier to manage and deploy than the previous manual script-based method.</p>

2021 ◽  
Author(s):  
◽  
David Stirling

<p>Client honeypots are devices for detecting malicious servers on a network. They interact with potentially malicious servers and analyse the Web pages returned to assess whether these pages contain an attack. This type of attack is termed a 'drive-by-download'. Low-interaction client honeypots operate a signature-based approach to detecting known malicious code. High- interaction client honeypots run client applications in full operating systems that are usually hosted by a virtual machine. The operating systems are either internally or externally monitored for anomalous behaviour. In recent years there have been a growing number of client honeypot systems being developed, but there is little interoperability between systems because each has its own custom operational scripts and data formats. By creating interoperability through standard interfaces we could more easily share usage of client honeypots and the data collected. Another problem is providing a simple means of managing an installation of client honeypots. Work ows are a popular technology for allowing end-users to co-ordinate e-science experiments, so these work ow systems can potentially be utilised for client honeypot management. To formulate requirements for management we ran moderate-scale scans of the .nz domain over several months using a manual script-based approach. The main requirements were a system that is user-oriented, loosely-coupled, and integrated with Grid computing|allowing for resource sharing across organisations. Our system design uses Grid services (extensions to Web services) to wrap client honeypots, a manager component acts as a broker for user access, and workflows orchestrate the Grid services. Our prototype wraps our case study - Capture-HPC -with these services, using the Taverna workflow system, and a Web portal for user access. When evaluating our experiences we found that while our system design met our requirements, currently a Java-based application operating on our Web services provides some advantages over our Taverna approach - particularly for modifying workflows, maintainability, and dealing with  failure. The Taverna workflows, however, are better suited for the data analysis phase and have some usability advantages. Workflow languages such as Taverna are still relatively immature, so improvements are likely to be made. Both of these approaches are significantly easier to manage and deploy than the previous manual script-based method.</p>


2021 ◽  
Vol 235 ◽  
pp. 02038
Author(s):  
Xi Zeng ◽  
Yu Zhou ◽  
Xuqi Chen

The development of the times and the development of the Internet have changed people’s consumption concepts. The author has conducted user research on user groups such as college students. After data analysis, the demand for resource sharing and trading of second-hand goods of college students was transformed into the function point of the trading platform. The APP was designed and developed to solve the needs of college students to share and exchange resources on campus. The APP’s main functions are second-hand commodity trading and virtual resource trading.


2012 ◽  
Vol 433-440 ◽  
pp. 3895-3899 ◽  
Author(s):  
Ray I Chang ◽  
Chi Cheng Chuang

Traditional NM (Network Management) techniques can not be applied on WSN (Wireless Sensor Network) due to its features of low computing ability, tiny memory space, and limited energy. A new NMA (Network Management Architecture) for WSN is needed. In this paper, we design a loosely coupled NMA of WSN based on SOA (Service-Oriented Architecture), and have well defined NM interfaces. Finally, we develop a SOA platform for WSN operations according to the NMA. Based on SOA platform, users can compose and use various NM Web Services by internet depending on their requirements. Heavy tasks which need a great deal of computing resources and storage are executed on the SOA platform. Thus, energy consumption and node computation can be decreased. Moreover, external applications use Web Services to integrate SOA platform for WSN. It lowers the difficulty in integrating different sensor platforms and heterogeneous devices.


Author(s):  
Furkh Zeshan ◽  
Radziah Mohamad ◽  
Mohammad Nazir Ahmad

Embedded systems are supporting the trend of moving away from centralised, high-cost products towards low-cost and high-volume products; yet, the non-functional constraints and the device heterogeneity can lead to system complexity. In this regard, Service-Oriented Architecture (SOA) is the best methodology for developing a loosely coupled, dynamic, flexible, distributed, and cost-effective application. SOA relies heavily on services, and the Semantic Web, as the advanced form of the Web, handles the application complexity and heterogeneity with the help of ontology. With an ever-increasing number of similar Web services in UDDI, a functional description of Web services is not sufficient for the discovery process. It is also difficult to rank the similar services based on their functionality. Therefore, the Quality of Service (QoS) description of Web services plays an important role in ranking services within many similar functional services. Context-awareness has been widely studied in embedded and real-time systems and can also play an important role in service ranking as an additional set of criteria. In addition, it can enhance human-computer interaction with the help of ontologies in distributed and heterogeneous environments. In order to address the issues involved in ranking similar services based on the QoS and context-awareness, the authors propose a service discovery framework for distributed embedded real-time systems in this chapter. The proposed framework considers user priorities, QoS, and the context-awareness to enable the user to select the best service among many functional similar services.


Author(s):  
Yinsheng Li ◽  
Hamada Ghenniwa ◽  
Weiming Shen

Current efforts have not enforced Web services as loosely coupled and autonomous entities. Web services and software agents have gained different focuses and accomplishments due to their development and application backgrounds. This chapter proposes service-oriented agents (SOAs) to unify Web services and software agents. Web services features can be well realized through introducing software agents’ sophisticated software modeling and interaction behaviors. We present a natural framework to integrate their related technologies into a cohesive body. Several critical challenges with SOAs have been addressed. The concepts, system and component structures, a meta-model driven semantic description, agent-oriented knowledge representation, and an implementation framework are proposed and investigated. They contribute to the identified setbacks with Web services technologies, such as dynamic composition, semantic description, and implementation framework. A prototype of the proposed SOAs implementation framework has been implemented. Several economic services are working on it.


Author(s):  
Gergely Sipos ◽  
Péter Kacsuk

This chapter summarizes the most relevant results that grid research achieved in the last decade, it presents the actual issues of the topic, and it outlines how current and future results from this area can contribute to smart organizations. At the first place the basic goal of the Grid is presented and its state-of-the-art, service-based realization is discussed. This global infrastructure will one day connect together diverse types of hardware and software elements, abstracting them out as intelligent autonomous agents that can discover and collaborate with each other on demand. The middle part of the chapter introduces two potential middleware technologies that service grids can be built on. They are the Web services-based open grid services architecture (OGSA) and Jini. The final part of the chapter presents the future of service grids and the important role these flexible infrastructures will probably have in the life of smart organizations.


Author(s):  
Manuel Palomo-Duarte

Web services are changing software development thanks to their loosely coupled nature and simple adoption. They can be easily composed to create new more powerful services, allowing for large programming systems. Verification and validation techniques try to find defects in a program to minimize losses that its malfunction could cause. Although many different approaches have been developed for “traditional” program testing, none of them have proven definitive. The problem is even more challenging for new paradigms like web services and web service compositions, because of their dynamic nature and uncommon web service-specific instructions. This chapter surveys the different approaches to web service and web service composition verification and validation, paying special attention to automation. When no tools are available for a given technique, academic efforts are discussed, and challenges are presented.


Author(s):  
Stéphanie Chollet ◽  
Philippe Lalanda ◽  
Jonathan Bardin

The visionary promise of Service-Oriented Computing (SOC) is a world-scale network of loosely coupled services that can be assembled with little effort in agile applications that may span organizations and computing platforms. In practice, services are assembled in a Service-Oriented Architecture (SOA) that provides mechanisms and rules to specify, publish, discover and compose available services. The aim of this chapter is to present the different technologies implementing the new paradigm of SOA: Web Services, UPnP, DPWS, and service-oriented component OSGi and iPOJO. These technologies have been developed and adapted to multiple domains: application integration, pervasive computing and dynamic application integration.


Author(s):  
Carlos Granell ◽  
Laura Díaz ◽  
Michael Gould

The development of geographic information systems (GISs) has been highly influenced by the overall progress of information technology (IT). These systems evolved from monolithic systems to become personal desktop GISs, with all or most data held locally, and then evolved to the Internet GIS paradigm in the form of Web services (Peng & Tsou, 2001). The highly distributed Web services model is such that geospatial data are loosely coupled with the underlying systems used to create and handle them, and geospatial processing functionalities are made available as remote, interoperable, discoverable geospatial services. In recent years the software industry has moved from tightly coupled application architectures such as CORBA (Common Object Request Broker Architecture?Vinoski, 1997) toward service-oriented architectures (SOAs) based on a network of interoperable, well-described services accessible via Web protocols. This has led to de facto standards for delivery of services such as Web Service Description Language (WSDL) to describe the functionality of a service, Simple Object Access Protocol (SOAP) to encapsulate Web service messages, and Universal Description, Discovery, and Integration (UDDI) to register and provide access to service offerings. Adoption of this Web services technology as an option to monolithic GISs is an emerging trend to provide distributed geospatial access, visualization, and processing. The GIS approach to SOA-based applications is perhaps best represented by the spatial data infrastructure (SDI) paradigm, in which standardized interfaces are the key to allowing geographic services to communicate with each other in an interoperable manner. This article focuses on standard interfaces and also on current implementations of geospatial data processing over the Web, commonly used in SDI environments. We also mention several challenges yet to be met, such as those concerned with semantics, discovery, and chaining of geospatial processing services and also with the extension of geospatial processing capabilities to the SOA world.


Author(s):  
Juan Manuel Adán-Coello

Service-oriented computing (SOC) is a new computing paradigm that uses services as building blocks to accelerate the development of distributed applications in heterogeneous computer environments. SOC promises a world of cooperating services where application components are combined with little effort into a network of loosely coupled services for creating flexible and dynamic business processes that can cover many organizations and computing platforms (Chesbrough & Spohrer, 2006; Papazoglou & Georgakopoulos, 2003). From a technical point of view, the efforts to offer services have focused on the development of standards and the creation of the infrastructure necessary to describe, discover, and access services using the Web. This type of service is usually called a Web service. The availability of an abundant number of Web services defines a platform for distributed computing in which information and services are supplied on demand, and new services can be created (composed) using available services. Nevertheless, the composition of Web services involves three fundamental problems (Sycara, Paolucci, Ankolekar, & Srinivasan, 2003): 1. To elaborate a plan that describes how Web services interact, how the functionally they offer can be integrated to provide a solution to the considered problem. 2. To discover Web services that accomplish the tasks required by the plan. 3. To manage the interaction of the chosen services. Problems 2 and 3 are of responsibility of the infrastructure that supports the composition of services, while the first problem is of responsibility of the (software) agents that use the infrastructure. The discovery and interaction of Web services poses two main challenges to the infrastructure: 1. How to represent Web services capabilities and how to recognize the similarities between service capabilities and the required functionalities. 2. How to specify the information a Web service requires and provides, the interaction protocol, and the low-level mechanisms required to service invocation.


Sign in / Sign up

Export Citation Format

Share Document