Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analytics

5/8/2006
06:00 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

SOA Interoperability Not Enough

WS-Policy interoperation is a good start, but more needs to be done

Layer 7 Technologies last week announced the interoperability of its security technology with application servers from several major vendors, using a proposed standard that could lead to easier security administration in Web services environments.

The XML gateway company said it has achieved interoperability with app servers and middleware from IBM, SAP, BEA, Sun, and Microsoft, using Web Services Policy (WS-Policy), which defines a framework for the use and transport of Web services.

The WS-Policy specification will make it easier for Web services users to define the requirements--including security rules--for linking Web services applications. For example, a WS-Policy could require that a request be encrypted and signed with a specific algorithm, or that it should be compressed. Web services use the policy to establish a trusted interface between applications and ensure that security requirements have been met.

"The WS-* suite is full of specifications no one needs, but WS-Policy is critical for centralized management, change control, and rapid deployment of services," says Scott Morrison, Director of Architecture for Layer 7.

Anne Thomas Manes, VP and research director at Burton Group, agrees. "The lack of a standardized policy framework is a big hole, and needs to get standardized as quickly as possible. Today, there is no centralized way to configure Web services, which means Web services need to be configured individually."

The WS-Policy specification was submitted to the W3C on April 25, and still must work its way through the standardization process. "Demonstrating interoperability is important, because it shows the industry and standards bodies that interoperability is practical today," says Phil Watson, senior product manager for Layer 7.

Thomas Manes and other experts agree that standardization and limited interoperability are a good start. But until the Web Services Interoperability (WS-I) group publishes an interoperability profile that removes ambiguity in the specifications, the value of an interoperability test is limited, they say.

Final approval of the WS-I profiles is still at least a year or two away, according to observers. In the meantime, enterprises should require vendors to demonstrate interoperability between products or use a Web services proxy to do the work, experts advise.

— Mike Fratto, Editor at Large, Dark Reading

Organizations mentioned in this story

  • BEA Systems Inc. (Nasdaq: BEAS)
  • IBM Corp. (NYSE: IBM)
  • Microsoft Corp. (Nasdaq: MSFT)
  • SAP AG (NYSE/Frankfurt: SAP)
  • Sun Microsystems Inc. (Nasdaq: SUNW)

    Mike Fratto is a principal analyst at Current Analysis, covering the Enterprise Networking and Data Center Technology markets. Prior to that, Mike was with UBM Tech for 15 years, and served as editor of Network Computing. He was also lead analyst for InformationWeek Analytics ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    News
    Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
    Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
    Edge-DRsplash-10-edge-articles
    Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
    Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
    News
    Cybercrime Groups More Prolific, Focus on Healthcare in 2020
    Robert Lemos, Contributing Writer,  2/22/2021
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Write a Caption, Win an Amazon Gift Card! Click Here
    Latest Comment: This comment is waiting for review by our moderators.
    Current Issue
    2021 Top Enterprise IT Trends
    We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
    Flash Poll
    Building the SOC of the Future
    Building the SOC of the Future
    Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2021-25284
    PUBLISHED: 2021-02-27
    An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
    CVE-2021-3144
    PUBLISHED: 2021-02-27
    In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
    CVE-2021-3148
    PUBLISHED: 2021-02-27
    An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
    CVE-2021-3151
    PUBLISHED: 2021-02-27
    i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...
    CVE-2021-3197
    PUBLISHED: 2021-02-27
    An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.