# WS-SecurityPolicy

CXF 2.2 introduced support for using [WS-SecurityPolicy](http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/ws-securitypolicy.html) to configure WSS4J instead of the custom configuration for WS-Security. However, all of the "background" material for WS-Security still applies and is important to know. WS-SecurityPolicy just provides an easier and more standards based way to configure and control the security requirements. With the security requirements documented in the WSDL as WS-Policy fragments, other tools such as .NET can easily know how to configure themselves to inter-operate with CXF services.

### In this section

* [Enabling WS-SecurityPolicy](https://help.qlik.com/talend/en-US/esb-service-developer-guide/7.3/enabling-ws-securitypolicy)
* [Policy description](https://help.qlik.com/talend/en-US/esb-service-developer-guide/7.3/policy-description)
* [Configuring the extra properties](https://help.qlik.com/talend/en-US/esb-service-developer-guide/7.3/configuring-extra-properties)