---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Enable contextual security plugin \[Updated in Security Center 1.3\]

# Enable contextual security plugin \[Updated in Security Center 1.3\] {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Activate the Contextual Security Plugin (com.glide.role_management) plugin to enable contextual security, which secures a record/information using create, read, write, and delete functionality.
After it is installed and activated, the dictionary roles (created by simple security manager) are no longer tested. Instead, the ServiceNow AI Platform looks for ACL rules on fields and tables. It secures the data with the help of ACL rules instead of traditional, role-based dictionary rules implemented by simple security manager. Even if you
configure the dictionary form and add roles to a dictionary entry, no change in rights occurs.

## More information {#sc-contextual-security-plugin__section_more_information}

{#sc-contextual-security-plugin__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Plugin ID | com.glide.role_management |
| Configuration type | System Definition \> Plugins |
| Category | [Access control](https://servicenow-prod.fluidtopics.net/xAmazkRh5FKyeb7q4TQGWw "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Purpose | Unlike the simple security manager, the contextual security manager is aware of the system table hierarchy. You can potentially have different security rules for a field based on where in the hierarchy it appears. |
| Recommended value | Active |
| Default value | There is no default value as this is a plugin, not a Glide property. |
| Security risk rating | 8.1 |
| Functional impact | This remediation enforces functional level of access controls, which would let application determine the access restrictions based on ACL table alone. |
| Security risk | (High) Functional level access controls must be enforced from the server side prior to executing CRUD operations, ensuring the appropriate level of access to instance users. |
| References | [Contextual Security Manager](https://servicenow-prod.fluidtopics.net/1DZbU1Rw7DlhjJnIKetbvg "Contextual Security Manager protects your data by controlling read, write, create, and delete authorization.") |
[ ]

{#sc-contextual-security-plugin__table_ajc_b43_3kb}