Create a new security policy

task australia Updated Sep 10, 2026 1 min read t_CreateANewSecurityPolicy.md

Administrators can specify which security profiles WS-Security communications must meet by creating a new security policy.

Before you begin

Role required: web_service_admin or admin

Procedure

Navigate to All > System Web Services > SOAP Security Policies.
Click New.

Fill out the SOAP Security Policy form (see table).

Field	Description
Name	Enter a unique name for the security policy. Use this name to set the default security policy with the `glide.soap.default_security_policy` property.
Type	Select whether the SOAP security policy applies to inbound or outbound traffic.
Required to Sign SOAP Request	Select this checkbox to require signed SOAP requests. Clear the checkbox to allow unsigned SOAP requests. When enabled, the instance will produce an error for any SOAP request that does not include a valid signature. When disabled, the instance still verifies any signature included with a SOAP request.
Authenticate	Select if a SOAP request must authenticate against all security profiles or at least one security profile.
Security Profiles	Select the security profiles you want to apply to this SOAP security policy. You must select at least one security profile.

Click Submit.

Parent Topic:SOAP web service

44 lines · 2.2 KB Wrap lines

---
title: Create a new security policy
description: Administrators can specify which security profiles WS-Security communications must meet by creating a new security policy.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/api-reference/web-services/t\_CreateANewSecurityPolicy.html
release: australia
product: Web Services
classification: web-services
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [SOAP web service, Inbound, Web services, API implementation, API implementation and reference]
---

# Create a new security policy

Administrators can specify which security profiles WS-Security communications must meet by creating a new security policy.

## Before you begin

Role required: web\_service\_admin or admin

## Procedure

1.  Navigate to **All** &gt; **System Web Services** &gt; **SOAP Security Policies**.

2.  Click **New**.

3.  Fill out the SOAP Security Policy form \(see table\).

    |Field|Description|
    |-----|-----------|
    |Name|Enter a unique name for the security policy. Use this name to set the default security policy with the `glide.soap.default_security_policy` property.|
    |Type|Select whether the SOAP security policy applies to inbound or outbound traffic.|
    |Required to Sign SOAP Request|Select this checkbox to require signed SOAP requests. Clear the checkbox to allow unsigned SOAP requests. When enabled, the instance will produce an error for any SOAP request that does not include a valid signature. When disabled, the instance still verifies any signature included with a SOAP request.|
    |Authenticate|Select if a SOAP request must authenticate against all security profiles or at least one security profile.|
    |Security Profiles|Select the [security profiles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/ws-security-reference.md) you want to apply to this SOAP security policy. You must select at least one security profile.|

4.  Click **Submit**.


**Parent Topic:**[SOAP web service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/c_SOAPWebService.md)