Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Mehdi Daoudi, Liz McMillan, Flint Brenton

Related Topics: Microservices Expo

Microservices Expo: Article

Enterprise Web Services Security: A Reference Architecture, part II

Focus on design and functionality

Last month (WSJ, Vol. 4, issue 2), we looked at how Web services should not depend on specific security environments and rules but should be managed as part of all of an enterprise's corporate data assets such as Web applications, ERP systems, and in-house applications.

We recommended that Web services security be integrated with the overall enterprise security infrastructure at the very beginning of the Web services deployment phase. This month, we'll look at some of those possible deployment models.

Deployment Models
There are four deployment models based on the guidelines presented in our earlier article.

Terminology
The terms used in the deployment models are defined as follows:

  • Reverse proxy server: Intermediary server (e.g., a Web server) configured to filter requests coming from Internet users into the enterprise, providing security, management, and caching capabilities.
  • User repository (or user store): A persistent data store that maintains user information. A user repository can be implemented in LDAP, RDBMS, Microsoft's Active Directory, and mainframe applications. Information related to a single user may be maintained in multiple, separate user stores, each of which needs to be queried for authentication and authorization purposes.
  • Web Services Management Point (WSMP): Enforcement point for implementing a Web service management policy
  • Web Services Security Enforcement (WSSE): Enforcement point for implementing a Web service security policy
Simple Proxy Deployment
Access to enterprise resources is achieved via a reverse proxy server. The first line of defense is the network firewall, which filters requests to the reverse proxy server (see Figure 1).

The request for a Web service is submitted using a SOAP message that can be sent over a variety of transport protocols (HyperText Transport Protocol [HTTP], Simple Mail Transport Protocol [SMTP], File Transfer Protocol [FTP], Java Message Service [JMS], and other message queue [MQ] services). The sender's identity is expressed in transport protocol headers or in the SOAP document submitted for the request. WSSE authenticates against the submitted credentials, binds the message to an identity, and, if authorized, grants access to the Web service.

The outer network firewall ensures that resources cannot be accessed externally. The inner network firewall ensures that the enterprise resources (including the IAM security policies and the user repositories) are protected against internal attacks.

Low-level access control methods are used to ensure that only the reverse proxy server can forward requests to back-end resources. This means that back-end resources (.NET, J2EE, and legacy) require additional container-level security configuration outside the IAM policy model.

WSSE enforces security across all types of transport. It supports both inbound and outbound flows (i.e., requests received by the enterprise from a third party and requests sent by the enterprise to a third-party). WSSE communicates with the IAM security policy server for security policy decisions.

This deployment template does not include many moving parts and does not require a complex and costly implementation. On the other hand, it does not scale very well because the container of each back-end resource needs its own access management layer.

Full IAM Deployment
All of the enterprise resources are protected by a single IAM system. WSSE points for J2EE and .NET containers may be deployed in two ways:

  • Interceptors (or "agents"): The agent can be integrated with a variety of Web services containers. The agent interacts with the IAM policies to provide security services.
  • SOAP message handlers: Use either the Java API for XML-based remote procedure calls (JAX-RPC) or .NET pipelines. SOAP message handlers have the benefit of being transport independent.
Legacy applications continue to use proprietary security but may synchronize with the enterprise user repositories. SAML may be used as a means of communicating with "opaque" containers that cannot accommodate WSSE points, such as legacy applications or more proprietary application servers (see Figure 2).

Once a Web service requester has successfully been identified, authenticated, and authorized, the IAM platform provides the ability to leverage the user identity to personalize the behavior of the Web service.

The Web service can be bound to aspects of an identity through user entitlement information passed to the Web service by the IAM platform. For example, when a user has successfully been authenticated and authorized to access a Web service, the IAM platform can identify which entitlements should be obtained about that user, retrieve them from the user store(s), and associate them with the Web service request by binding them to the XML message.

This eliminates the need for a Web service to keep its own entitlement database and handle the retrieval of entitlements in the application logic. Thanks to the IAM platform, these entitlements can be centrally and securely managed and associated directly with a user's identity.

In some variations of this deployment model, the reverse proxy is optional.

IAM + WSM Deployment
The SOAP message is first received by the WSM enforcement point (WSMP). The WSMP makes a call to the WSSE point to ensure that the SOAP flow is secured.

WSSE authenticates the requester against IAM policies and returns security information to the WSMP. The WSMP can then enforce the WSM policy once the SOAP message is bound to a Web service consumer's identity.

The WSM platform can integrate with the IAM platform in two ways:

  • The WSM platform can explicitly invoke the WSSE through the IAM application programming interface (API)
  • The WSM platform can use the WSSE agent or the message handler model described above.
In this deployment model, the WSM platform takes advantage of the IAM platform, which links it to the enterprise-wide IAM infrastructure (see Figure 3).

This deployment model allows the enterprise to leverage a corporate infrastructure for security (the IAM platform) and Web services management (the WSM platform). Both provide a layer of abstraction that relieves Web services developers from security and management tasks so that they can concentrate on the design of the Web service business functions.

Network Appliance Deployment
This is the full-blown integration including a network appliance. The network appliance is added to provide wire-speed XML processing (see Figure 4).

In this deployment model, the network appliance delivers network security services combined with an authentication service, as described last month (see Protection and Threat Prevention Layer).

Typically, the network appliance interacts with Web services flows by intercepting the incoming request as soon as it passes through the network firewall. The network appliance decrypts the request, parses the XML document, validates the document against an XML Schema, and applies transformations if required.

The network appliance may provide authentication against a user store configured with the IAM platform. The result of authentication is then communicated downstream, using SAML for example. The WSSE and WSM enforcement points can also benefit from authentication information provided by the network appliance.

Once the Web service requester is authenticated, the IAM platform can move to grant access to the Web service, and the WSM system can apply business-level management policies.

Conclusion
With a focus on security and management, a Web Services Reference Architecture can help the prevention (network security), enablement (identity and access management), and enforcement (Web services management) layers of a Web services architecture fit together.

Web services providers can focus on the design and functionality of the Web services they expose to their employees, customers, or partners, while relying on enterprise-wide security and management services that increase overall availability, scalability, interoperability, and manageability.

References

  • www.w3.org/XML: The W3C's XML 1.0 Second Edition Recommendation describes the Extensible Markup Language (XML), "the universal format for structured documents and data on the Web."
  • www.w3.org/Security: The W3C's security-resources home page includes many links to various aspects of Web and Internet security (cryptography, authentication, authorization, etc.).
  • http://searchwebservices.techtarget.com: Web services–specific information resource for enterprise IT professionals Includes useful articles and technical notes covering all aspects of Web services, in particular security.
  • www.w3.org/DSig/Overview.html: The W3C's XML Signature (XML-DSIG) Recommendation describes digital signatures as applied to XML documents.
  • www.w3.org/Encryption/2001: The W3C's XML Encryption Recommendation defines a process for encrypting and decrypting XML documents.
  • www.w3.org/TR/xkms: The W3C's XML Key Information Service Specification (XKMS) Recommendation defines protocols for distributing and registering public keys, used together with XML Signature and XML Encryption.
  • http://xml.coverpages.org/xrml.html: The Extensible Rights Markup Language (XrML) home page.
  • www.oasis-open.org/committees/security: The OASIS specification for the Security Assertion Markup Language (SAML) defines an XML-based security framework for exchanging authentication and authorization information.
  • www.w3.org/TR/SOAP: The W3C's SOAP Recommendation (v1.1) describes the Simple Object Access Protocol, designed as a messaging framework for exchanging XML documents between peers in a platform-neutral environment.
  • www.oasis-open.org/committees/ wss/documents/WSS-Core-08-1212-merged.pdf: Working draft of the Web Services Security core specification.
  • www.w3.org/TR/wsdl: The W3C's WSDL submission specifies the Web Services Description Language, a framework providing definitions for network services and the automation of application communication through XML documents.
  • www.uddi.org/about.html: The Universal Description, Discovery, and Integration (UDDI) project is an industry initiative designed to create an XML framework for describing Web services providers and a description of the services they provide.
  • More Stories By Marc Chanliau

    Marc Chanliau has been in the software industry for more than 20 years and is currently a director of product management at Oracle where he is responsible for Identity Management solutions and innovations. He is heavily involved in security and XML standards groups including serving as the first chair person of the OASIS Security Services Technical Committee (SSTC), which culminated in the adoption of SAML as an official OASIS standard, participating on the WS-Security Technical Committee, helping to define the Liberty Alliance 2.0 specifications, and participating in the Java Specification Request (JSR) committee.

    More Stories By Prateek Mishra

    Prateek Mishra, Ph.D. has more than ten years experience with enterprise-class distributed systems. He is Director of Technology at Netegrity and works on Strategy and Standards. He was an Editor of the SAML 1.0 specification and is co-chair of the SSTC (SAML) Committee and participates in the WSS (WS-Security) Committee.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    @MicroservicesExpo Stories
    Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
    Today companies are looking to achieve cloud-first digital agility to reduce time-to-market, optimize utilization of resources, and rapidly deliver disruptive business solutions. However, leveraging the benefits of cloud deployments can be complicated for companies with extensive legacy computing environments. In his session at 21st Cloud Expo, Craig Sproule, founder and CEO of Metavine, will outline the challenges enterprises face in migrating legacy solutions to the cloud. He will also prese...
    DevOps at Cloud Expo – being held October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real r...
    ‘Trend’ is a pretty common business term, but its definition tends to vary by industry. In performance monitoring, trend, or trend shift, is a key metric that is used to indicate change. Change is inevitable. Today’s websites must frequently update and change to keep up with competition and attract new users, but such changes can have a negative impact on the user experience if not managed properly. The dynamic nature of the Internet makes it necessary to constantly monitor different metrics. O...
    With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, security is the highest adoption barrier. Is your organization ready to address the security risks with containers for your DevOps environment? In his session at @DevOpsSummit at 21st Cloud Expo, Chris Van Tuin, Chief Technologist, NA West at Red Hat, will discuss: The top security r...
    The last two years has seen discussions about cloud computing evolve from the public / private / hybrid split to the reality that most enterprises will be creating a complex, multi-cloud strategy. Companies are wary of committing all of their resources to a single cloud, and instead are choosing to spread the risk – and the benefits – of cloud computing across multiple providers and internal infrastructures, as they follow their business needs. Will this approach be successful? How large is the ...
    Enterprises are moving to the cloud faster than most of us in security expected. CIOs are going from 0 to 100 in cloud adoption and leaving security teams in the dust. Once cloud is part of an enterprise stack, it’s unclear who has responsibility for the protection of applications, services, and data. When cloud breaches occur, whether active compromise or a publicly accessible database, the blame must fall on both service providers and users. In his session at 21st Cloud Expo, Ben Johnson, C...
    Many organizations adopt DevOps to reduce cycle times and deliver software faster; some take on DevOps to drive higher quality and better end-user experience; others look to DevOps for a clearer line-of-sight to customers to drive better business impacts. In truth, these three foundations go together. In this power panel at @DevOpsSummit 21st Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, industry experts will discuss how leading organizations build application success from all...
    Most of the time there is a lot of work involved to move to the cloud, and most of that isn't really related to AWS or Azure or Google Cloud. Before we talk about public cloud vendors and DevOps tools, there are usually several technical and non-technical challenges that are connected to it and that every company needs to solve to move to the cloud. In his session at 21st Cloud Expo, Stefano Bellasio, CEO and founder of Cloud Academy Inc., will discuss what the tools, disciplines, and cultural...
    The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
    As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
    Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
    The nature of the technology business is forward-thinking. It focuses on the future and what’s coming next. Innovations and creativity in our world of software development strive to improve the status quo and increase customer satisfaction through speed and increased connectivity. Yet, while it's exciting to see enterprises embrace new ways of thinking and advance their processes with cutting edge technology, it rarely happens rapidly or even simultaneously across all industries.
    These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
    21st International Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Me...
    DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
    "NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    One of the biggest challenges with adopting a DevOps mentality is: new applications are easily adapted to cloud-native, microservice-based, or containerized architectures - they can be built for them - but old applications need complex refactoring. On the other hand, these new technologies can require relearning or adapting new, oftentimes more complex, methodologies and tools to be ready for production. In his general session at @DevOpsSummit at 20th Cloud Expo, Chris Brown, Solutions Marketi...
    You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
    Hypertext Transfer Protocol, or HTTP, was first introduced by Tim Berners-Lee in 1991. The initial version HTTP/0.9 was designed to facilitate data transfers between a client and server. The protocol works on a request-response model over a TCP connection, but it’s evolved over the years to include several improvements and advanced features. The latest version is HTTP/2, which has introduced major advancements that prioritize webpage performance and speed.