Home > Articles > Security > Network Security

Web Service Security Architectures, Part I

Web services security architectures represent a conglomeration of different pieces of security technologies. Seshadri Gokul discusses some of the common aspects of a comprehensive Web services security architecture, including problems and challenges.
Like this article? We recommend

In a sense, the articles in this series have discussed XML security, rather than Web services security. The topics included SAML, XML encryption, XML digital signatures and XKMS. All of them discussed XML security aspects in detail, not Web services security in particular.

Partly, this is because Web services security architecture as a whole is built around these small bits and pieces. XML is the foundation of Web services, and we can leverage whatever technologies we have built for securing XML to also secure Web services.

Moreover, Web services technology itself is in its very early stages, and neutral bodies and consortia are working hard to evolve common Web services security specifications that are acceptable to all vendors and platforms. Thus, standardization has just begun with XML security specifications, and down the line it will be extended to Web services as well.

This article discusses some of the common aspects of a comprehensive Web services security architecture—the problems and challenges it poses. Next, there is a discussion of WS Security, a major Web services security model initiative pioneered by IBM and Microsoft.

Web Services Security Models

When thinking about a comprehensive security model for Web services, the first thing that strikes us is that it is not point-to-point security for which we have so many solutions in place. All security models that have evolved so far have been based on a client/server model, which is essentially point-to-point security.

For example, a sender of a confidential message encrypts and signs the message using the receiver's public key, and transmits it across the wire. The receiver decrypts the message using his public key. This model works well if only two parties are involved in the communication; if a third party is introduced in the middle, the model collapses.

In Web services, we see several services interacting with each other in a random manner. For example, a feed rate service may have the option to select either service A or B at random, based upon certain criteria such as availability, quality of service, cost, and so on. Now, how are we to provide security to such a transaction, which doesn't even follow the same structure for each transaction? The confusion only compounds further if we think about dynamic Web services, in which the feed rate service may not even know beforehand whether its choice is limited to service A and B.

As we think further about this security model for Web services, we will find that the challenges we have to address are related to business (how to dynamically establish partnerships, evolve trusted service federations, and so on) as well as technology (message security, encryption/decryption, public keys exchange, etc.).

Ideally, the participating Web services in a transaction should not bother much about security aspects in the communication, and the underlying security infrastructure should transparently provide a basic security layer for the confidential XML data exchanged—such as data integrity, confidentiality, and non-repudiation.

Let's consider two simple Web services interaction scenarios, and discuss the security issues that come to play and how we can address them.

In scenario 1 (see Figure 1), Service A transmits some XML information to Service B, which in turn adds some more data and passes it on to Service C (the end consumer). The entire communication must be secure and confidential.

Figure 1Figure 1 Web services interaction: scenario 1.

Let's assume that all three services are processed by three different systems, and there is no level of trust or relationship between them.

Now, how can we secure this communication?

One option is this: Service A can encrypt the data it is sending by using Service C's public key. It can also sign the document by using XML digital signatures in order to take responsibility for what it is sending. Service B just adds some more information to the data stream so it can also make use of Service C's public key to encrypt the data and sign it, if need be.

Service C, upon receiving the document, can decrypt the data by using its private key. It can also ensure that the document has not been tampered with while in transit by using the XML signatures.

Sounds very simple, eh?

Remember that Service A's transmission was encrypted and signed. Service B can encrypt and sign the document further (encryption over already encrypted data), or it can append its own encrypted portions to the document. Service C needs to be aware of this methodology, so that it can decrypt the document accordingly. Also, the verification of signatures at Service C implies that Services A and B have public and private keys that need to be appropriately transmitted to Service C. Apart from the complexity of maintaining and transmitting public and private keys at each service, the overhead of encryption/decryption and digital signature verification cycles is very substantial. Repeating this cycle over and over again for each and every transaction will only have a negative effect on the overall performance of the system.

Moreover, we have not discussed how Service A initially decided to work with Service B in order to deliver a secure document to Service C. Nor did we bother about how Service C entirely trusts the data coming from A and B.

From a business perspective, it is difficult to achieve such levels of trust across different functionally independent systems and domains.

As we delve deeper, we will hit many more issues, but this is just to illustrate that building security around what seems to be a simple Web service transaction is costly and sometimes complex.

Now, let's slightly modify this scenario to illustrate the loosely coupled model of Web services interactions (see Figure 2).

Let's say that Service A has the option of selecting Service B or D at random—based upon certain criteria—before the data is passed on to Service C for final consumption. Such run time decision-making capabilities make Web services much more attractive. For example, Service A can see whether Service B is available or not; if it is not available because of some reason, it can contact Service D, which in this case serves as a substitute for B.

Another example could be that Service B's commissions are attractive in some cases, whereas Service D is cost-effective in certain other cases.

Figure 2Figure 2 Web services interaction: scenario 2.

This simple change dramatically introduces several complexities into the security model.

Apart from the complexity of handling one more public and private key, Service C has to be made aware of whether Service B or D serviced this particular transaction, so the signature can be verified accordingly. As we keep adding more and more services, we end up with multitudes of key pairs and encryption/decryption/signing processes for a single transaction service. Moreover, we are already far from our ultimate goal of providing transparent security infrastructure to all participating services.

Thus, we have to radically rethink the way we have been defining our security architecture.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020