---
sourceDocument: Australia API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/api-reference

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Security

# Secure and protect a processor {#ariaid-title1}

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

You can protect your processor against unauthorized use by using role restrictions,
and protect it by requiring a CSRF token.

## Warum und wann dieser Vorgang ausgeführt wird

Hinweis:  
This feature is deprecated. While legacy, existing custom processors continue to be supported, creating new custom processors has been deprecated. Instead, use the [Scripted REST APIs](https://servicenow-prod.fluidtopics.net/eAgQ546WEOagLzEOTr_eqQ "The scripted REST API feature allows application developers to build custom web service APIs.").

You can re-use a table's user role restrictions to protect it from access by your
processor. This protection method assumes the processor will access table data.

## Prozedur

1. Create or select a user role that has access to the table the processor script calls.
2. Navigate to System DefinitionProcessors.
3. In Script, add the following code block.  

       var now_GR = new GlideRecord('your_table_name');
       // canRead() compares the table's ACL to the user making this request, and returns true if the logged-in user has read access to this table
       if(gr.canRead())  
       { 
         // Perform table query here  
         g_processor.writeOutput('Success!'); 
       } else { 
         g_processor.writeOutput('You do not have permission to read table your_table_name'); 
       }

4. Update the code block to use other access restrictions as needed.  
   Available access functions include:  
   * canCreate()
   * canRead()
   * canWrite()
   * canDelete()
   {#t_SecureAProcessor__ul_ccy_3z2_sr}
5. Click Update.

## Protect a processor with a CSRF token {#ariaid-title2}

You can protect a processor by requiring a CSRF token.

### Warum und wann dieser Vorgang ausgeführt wird

Script type processors can require a CSRF token check before the processor runs.

### Prozedur

1. Navigate to AllSystem DefinitionProcessors.
2. Open a processor record.
3. Select the CSRF protect option.
4. Click Update.
**Zugehörige Informationen**   

* [Assign a role to a user](https://www.servicenow.com/docs/access?context=t_AssignARoleToAUser&version=australia&pubname=australia-platform-administration&ft:locale=en-US)