Web Services Security 1.0, the foundation specification for creating a security infrastructure around Web services, officially became a standard Monday, paving the way for corporate adoption.The full membership of the Organization for the Advancement of Structured Information Standards (OASIS) gave final approval to the WS-Security specification two years after it was jointly submitted by Microsoft, IBM and VeriSign. Final approval of the standard included ratification of two profiles used with WS-Security, the Username Token Profile 1.0 and the X.509 Token Profile 1.0. Additional security profiles are under development within OASIS.In essence, WS-Security allows Web services to pass secure and signed messages. Security information is communicated by passing information in the headers of messages based on Simple Object Access Protocol (SOAP).\u201cWS-Security is essential for securing a Web services environment,\u201d says Jim Kobielus, an analyst with the Burton Group. \u201cIt is central to the core of standards everyone is implementing, including XML, SOAP and WSDL - so it\u2019s ratification is no surprise to anyone given the impressive amount of existing support and implementation.\u201dMajor vendors are already supporting WS-Security include BEA Systems, Computer Associates, HP, IBM, Microsoft, Novell, SAP, and Sun.\u201cApproval as an OASIS standard adds a level of acceptance for adoption in the marketplace,\u201d says Patrick Gannon, CEO of OASIS. \u201cWe\u2019ve seen a reluctance by end users to invest in moving targets. They want stability so they can reap ROI. Ratification is an important step to allow companies and governments to reference this standard specification in their projects.\u201dWS-Security, however, is not the end of the line. The specification is seen as an enabling technology for supporting simple message security all the way up to full-federated security.\u00a0Microsoft, IBM and other partners are still working on other specifications that use WS-Security as a foundation to supply other security services for Web services. All are in various forms of development, but none have been approved as a standard. They include WS-Policy for expressing security policies, WS-Trust for providing a model for direct and brokered trust relationships, WS-Privacy, for defining and implementing privacy practices, WS-Secure Conversation, for managing and authenticating message exchanges, WS-Federation, for managing and brokering trust relationships in a heterogeneous federated environment, and WS-Authorization, for defining how to manage authorization data and policies.