Secure data
Summarize
Summary of Secure data
Data security is a critical aspect of application development on the ServiceNow AI Platform. ServiceNow simplifies this by automatically configuring access controls for tables based on roles during creation, ensuring that only authorized users can read, create, write, or delete data. Properly configuring access control rules at both table and column levels is essential for protecting sensitive information and complying with platform subscription models.
Show less
Key Features
- Access Control Lists (ACLs): Combine multiple access controls to define fine-grained security rules for tables, UI pages, property pages, and other content.
- Role-based Access: Only users assigned appropriate roles can access or modify table data, with automatic configuration during table setup.
- Before-query Business Rules: These run prior to database queries and control read access at the record level without showing filtered records as restricted, unlike ACLs. They should be used sparingly and do not replace ACLs.
- Performance Considerations: Minimize GlideRecord queries in access control scripts to avoid negative impacts on performance.
- Subscription Model Impact: Access to tables counts towards subscription limits, so ACLs should be used to restrict table access appropriately to control costs.
- Encryption: The platform offers encryption at the application, database, and hardware tiers to enhance data protection.
Key Outcomes
- Ensures that only authorized users can access or modify sensitive data, maintaining compliance and security best practices.
- Helps optimize application performance by reducing inefficient queries in access controls.
- Supports subscription cost management by accurately restricting user access to necessary tables only.
- Provides layered data protection with encryption options across multiple tiers.
- Encourages early implementation of security configurations to avoid rework and integration issues later in the application development process.
Data security is one of the most important and overlooked aspects of creating an application. ServiceNow automatically configures access control for a new or selected role during the table creation process. Only users with the role can access the table to read, create, write, and delete.
Use access control rules to configure table and column-level security in the ServiceNow AI Platform. To properly configure access to an application, developers should understand how access controls work and the order in which access controls are evaluated. Apply multiple access controls that together make an Access Control List (ACL).
Self-Paced Training: Securing Applications
Documentation: Access control list rules
- Protect tables, UI pages, property pages, and other content with the appropriate access controls and roles.
- Limit the use of GlideRecord queries in access control scripts. GlideRecord queries can affect performance.
Alternately, secure data on the ServiceNow AI Platform with before-query Business Rules. Before-query Business Rules run before the database query and are limited to controlling read access to a record. Only use before-query Business Rules when necessary. Some considerations when deciding to use Access Controls or before-query Business Rules:
- GlideRecord queries will bypass read access controls on a table and will be restricted by before-query Business Rules on a table.
- When access controls restrict read access to records in a list, ServiceNow shows a message saying that access has been restricted for the records. With before-query Business Rules, the number of records in the list total matches the number of records shown to the user. The user receives no indication that some records have been hidden from the list.