SOA Explosion in Chemical Factory Layered representation of architecture

1) Not a technology but an architecture

2) Well defined business process as services
3)Connects separate technology systems
through web services
4)It uses reusable software components that
use a standardized messaging system-built
on internet based platform
5)Allows different kinds of systems and
platforms to communicate with each other
in a common language
6)Provides transparency of the process
7)SOA components are loosely coupled and
exposed as independent services on a
network.
8)SOA reduces development time,
promotes software reuse, and reduces
project costs.
9)SOA have been developed for server side
application integration and offer a set of
tools and paradigms to design distributed
applications

Mapping for our Scenario

Sensor Layer containing Sensors such as Acoustic Sensors, Cameras, Texts,
Lidar, Bering, Data from feed, Human in loop
Processing Layer contains
1) ASI : interfaces with the different nodes to receive information
2) Middleware core provides functionality for interaction between different
nodes
3) Hosted Intelligence provides processing functionalities in 2 forms : Hosted
Services : Contains our data processing algorithms like Ransac, HOG, SIFT,
Hough, Gaussian Mixture Models, Text Extractor and data fusion algorithms
Hosted Tasks : Consumes the data and services and provide high level
information and makes some decision.
Application Layer : Provides the IT backbone, like database servers, A priori
data , Raw Sensor Data, Synthetic Data, Extracted Data.
 Security Issues in SOA
SOA components are loosely coupled and exposed as independent services on a network. This flexibility also
posses serious security threats to the SOA- architecture. Some of the common security vulnerabilities in SOA are :
1) Injection Flaws
Injection flaws occur when software does not properly validate input. An attacker could craft malicious input that causes the Web Service
software to perform operations on behalf of the attacker. Classes of injection flaws include Cross Site Scripting, SQL Injection, and XPath
Injection.
2) XML Denial of Service Issues
XML is a versatile data encoding standard. However, parsing XML can be processor intensive and complex, which can lead to security
issues. One common issue is a denial of service (DOS) against a web service. If an attacker crafts an XML message with very large payloads,
recursive content, excessive nesting, malicious external entities, or with malicious DTDs (Data Type Documents), a DOS can occur.
3) Insecure Communications
Attackers can steal or modify information if not protected while in transit.
4) Information Leakage Web
Services that generate verbose fault messages are useful to developers and system administrators. However, the same messages can give
away too much information in operational environments. This issue also affects Web Services that use a WSDL to provide a description of
a service and its interface. A WSDL contains server directory information, internal IP address information, available services and
methods, and other critical information valuable to an attacker.
5) Replay Attack Flaws
Protecting a message against modification does not stop an attacker from replaying the message to a server to invoke actions multiple
times.
6) Insufficient Authentication Web
Services that perform sensitive functions should require authentication.
7) Inadequate Testing
Unidentified coding flaws in Web Services can lead to a compromise of sensitive information. Because SOA implementations typically
connect to backend servers, the consequences of a compromise are amplified.
8) Insecure Configuration and Logging
Web Services typically run on exposed, public facing servers, outside an organization’s security perimeter. Mistakes in configurations and
patch management of these servers can be catastrophic. Logs are of great use if an intrusion or hacking attempt occurs.