---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Use of secure insert multiple operation within import set API

# Use of secure insert multiple operation within import set API {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use the com.glide.import_set_api.insert_multiple_optimize property to control whether GlideRecordSecure or GlideRecord is used for the Insert Multiple operation within
the Import Set API.
The com.glide.import_set_api.insert_multiple_optimize system property controls whether GlideRecordSecure or GlideRecord is used for the Insert Multiple operation within Import Set API.

If this property is set to false, then GlideRecordSecure will be used to insert records and Table level ACLs will be evaluated.

If this property is set to true, then GlideRecord will be used to insert records and Table level ACLs will not be evaluated.

Ensure that the property com.glide.import_set_api.insert_multiple_optimize is set to false.  
Note:  
If this property must be set to true, then you must ensure that the Import Set API Insert Multiple REST Endpoint ACL (sys_id: 3101b770ff2211105cf343d0653bf182) is active and also audit user's who have the import_transformer role.

## More information {#sc-use-of-secure-insert-multiple-operation-within-import-set-api__section_qhx_1b1_xwb}

{#sc-use-of-secure-insert-multiple-operation-within-import-set-api__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | com.glide.import_set_api.insert_multiple_optimize |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | false |
| Default value | false |
| Fallback value | false |
| Category | [Access control](https://www.servicenow.com/docs/x7vcJqvJ0dwOasc9M2~48A "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.") |
| Security risk | * Severity score: 6.5 * CVSS score: Medium * Security risk details: If this property is not set to the recommended value of false, then a low privilege user may be able to insert data into tables outside the scope of their privileged roles. {#sc-use-of-secure-insert-multiple-operation-within-import-set-api__ul_g1g_3sf_xwb} |
| Dependencies and prerequisites | None |
| Functional impact | This property optimizes the performance of Import Set API by using GlideRecord to save data. When the parameter is set, it requires an integration user to have the import_transformer role to access the API. |
| References | <https://developer.servicenow.com/blog.do?p=/post/gliderecord-vs-gliderecordsecure> |
[ ]

{#sc-use-of-secure-insert-multiple-operation-within-import-set-api__table_ajc_b43_3kb}