IT Terminology-Concepts

XML Firewall

An XML firewall is a specialized device used to protect applications exposed through XML based interfaces like WSDL and REST and scan XML traffic coming in and out of an organization. Typically deployed in a DMZ environment an XML Firewall is often used to validate XML traffic, control access to XML based resources, filter XML content and rate limit requests to back-end applications exposed through XML based interfaces. XML Firewalls are commonly deployed as hardware but can also be found as software and virtual appliance for VMWare, Xen or Amazon EC2. A number of brands of XML Firewall exist and they often differ based on parameters like performance (with or without hardware acceleration, 32 Vs 64 bit), scalability (how do they cluster and perform under load), security certification (common criteria, FIPS being the most common), identity support (for SAML, OAuth, enterprise SSO solutions) and extensibility (they can support different transport protocols like IBM MQ, Tibco EMS, etc.). XML Firewalling functionality is typically embedded inside XML Appliances and SOA Gateways.

ESB

Enterprise Service Bus - An enterprise service bus (ESB) is a software architecture model used for designing and implementing communication between mutually interacting software applications in a service-oriented architecture (SOA). As a software architectural model for distributed computing it is a specialty variant of the more general client server model and promotes agility and flexibility with regards to communication between applications. Its primary use is in enterprise application integration (EAI) of heterogeneous and complex landscapes. http://en.wikipedia.org/wiki/Enterprise_service_bus

EAI

Enterprise application integration - the use of software and computer systems architectural principles to integrate a set of enterprise computer applications. Enterprise application integration is an integration framework composed of a collection of technologies and services which form a middleware to enable integration of systems and applications across the enterprise. http://en.wikipedia.org/wiki/Enterprise_application_integration

SOA

Service-oriented architecture (SOA) is a software design and software architecture design pattern based on discrete pieces of software providing application functionality as services to other applications. This is known as service-orientation. It is independent of any vendor, product or technology.[1] A service is a self-contained unit of functionality, such as retrieving an online bank statement.[2] Services can be combined by other software applications to provide the complete functionality of a large software application.[3] SOA makes it easy for computers connected over a network to cooperate. Every computer can run an arbitrary number of services, and each service is built in a way that ensures that the service can exchange information with any other service in the network without human interaction and without the need to make changes to the underlying program itself. http://en.wikipedia.org/wiki/Service-oriented_architecture

UDDI

Universal Description, Discovery and Integration (UDDI, pronounced Yu-diː) is a platform-independent, Extensible Markup Language (XML)-based registry by which businesses worldwide can list themselves on the Internet, and a mechanism to register and locate web service applications. UDDI is an open industry initiative, sponsored by the Organization for the Advancement of Structured Information Standards (OASIS), for enabling businesses to publish service listings and discover each other, and to define how the services or software applications interact over the Internet. UDDI was originally proposed as a core Web service standard.[1] It is designed to be interrogated by SOAP messages and to provide access to Web Services Description Language (WSDL) documents describing the protocol bindings and message formats required to interact with the web services listed in its directory.

WSDM

Web Services Distributed Management (WSDM, pronounced wisdom) is a web service standard for managing and monitoring the status of other services. The goal of WSDM is to allow a well-defined network protocol for controlling any other service that is WSDM-compliant. For example, a third-party digital dashboard or network management system could be used to monitor the status or performance of other services, and potentially take corrective actions to restart services if failures occur. Some aspects of WSDM overlap or displace functionality of SNMP. WSDM consists of two specifications:[1] Management Using Web Services (MUWS) — WSDM MUWS defines how to represent and access the manageability interfaces of resources as Web services. It defines a basic set of manageability capabilities, such as resource identity, metrics, configuration, and relationships, which can be composed to express the capability of the management instrumentation. WSDM MUWS also provides a standard management event format to improve interoperability and correlation. Management Of Web Services (MOWS) — WSDM MOWS defines how to manage Web services as resources and how to describe and access that manageability using MUWS. MOWS provides mechanisms and methodologies that enable manageable Web services applications to interoperate across enterprise and organizational boundaries.

Common Criteria Mode

review