--- title: "Set Security and compliance studio parameters" slug: "set-security-and-compliance-studio-parameters" description: "Set up Security and Compliance Studio parameters, manage data migration, and enable enhanced segregation of duties for effective security management." tags: ["Task", "Security and Compliance Studio", "SCS"] updated: 2026-08-18T08:50:06Z published: 2026-08-18T08:50:06Z canonical: "docs.staedean.com/set-security-and-compliance-studio-parameters" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Set Security and compliance studio parameters Before you start using the Security and Compliance Studio, set the Security and Compliance Studio parameters. ### Steps 1. Click **Security management**. 2. Click **Parameters**. 3. Sub-task: Set general parameters. 1. You can define the default prefix for roles that are created in the Security and Compliance Studio. For example, if you create a role from **Match roles** or **Merge roles**. In the **Prefix** field, type a value. 2. You can use a color to highlight: Select **Yes** in the **Color for securable objects** field. > [!NOTE] > Note > > In the color box, you can move the + pointer to choose the desired color. - On the **Match roles** page, the duties and privileges with the same securable object as the already selected duties and privileges. These records are highlighted if you click **Find matched entry points**. - On the **Security explorer** to highlight, for the pinned record, the references with the highest user license type. 3. During implementation, to make security configuration event logging possible, you must once initialize the **Security and compliance studio IT audit**. If you run the **Security and compliance studio IT audit job** again, all logged events are deleted. You can lock this job to prevent the deletion of logged events. Select **Yes** in the **Lock 'Initialize Security and compliance IT audit' job** field. 4. You can define the number of snapshots that is kept if you delete snapshots automatically. In the **Limit number of snapshots** field, enter a number. 5. You can enable automatic updates of security configuration changes to the latest snapshot. So, no new snapshot is required each time you change the security configuration. Automatic updates of security configuration changes to the latest snapshot are done when you, for example: Select **Yes** in the **Enable dynamic snapshot** field. > [!NOTE] > Note > > If you use dynamic snapshots, you are advised to create a snapshot regularly. You do so to ensure that no security inconsistencies occur and to create a safety net, - Publish changes. - Approve security requests. - Update or create a role with the wizard. - Import security configurations. - Assign users to roles. 6. You can use a color to highlight securable objects that have access to sensitive data. These securable objects are highlighted on the: Select **Yes** in the **Highlight sensitive data over SCS** field. > [!NOTE] > Note > > In the color box, you can move the + pointer to choose the desired color. - **Create role wizard** - **Locked security roles** page - **Match roles** page 4. Sub-task: Manage data migration. 1. In Security and Compliance Studio, release 10.0.6.2, several data migration batch jobs are available. Run these batch jobs before you upgrade to future Security and Compliance Studio releases. This is required because of several data model changes and new data entities. You only need to run these batch jobs once. Click the **Data migration** tab. 2. Before you upgrade Security and Compliance Studio to release 10.0.6.2, and in your environment: Select **No** in the **Security scenarios migrated** field. - Security scenarios exist, select **No**. - No security scenarios exist, select **Yes**. 3. When you have upgraded Security and Compliance Studio to release 10.0.6.2 and security scenarios existed before the upgrade, migrate these security scenarios. Click **Migrate security scenarios**. > [!NOTE] > Note > > When the security scenarios are migrated, in the **Security scenarios migrated** field, select **Yes**. 4. Because of data model changes, the **Scenario data entity** must be recreated. As a result, the export and import of scenarios is enabled. Click **Update Scenario data entity**. 5. Securable objects such as roles, duties, privileges, and entry points are global. So, these are independent of companies. In Security and Compliance Studio, some of this data was stored per company. These tables are now also made global. On migration to release 10.0.6.2, all existing securable objects must be made global. If a securable object exists for several companies, the securable object of the current company is kept and made global. The same securable objects in the other companies are deleted. Click **Resolve cross-company data errors**. > [!NOTE] > Note > > Only run this batch job once. 5. Sub-task: Enable enhanced segregation of duties rules. 1. Click the **Enhanced SoD rules** tab. 2. With the enhanced segregation rules, you can not only define segregation rules on duty level, but also on privilege level, on entry point level, and with segregation security sets. Select **Yes** to use the enhanced segregation of duties functionality. As a result, you can set up and manage segregation rules on several levels. Also, segregation rule validations are done for the relevant levels. Select **Yes** in the **Enable enhanced SoD rules** field. 3. You can have existing segregation of duty rules when you switch to using enhanced segregation of duties rule. If so, copy the existing segregation of duty rules to the enhanced segregation of duty rules. Click **Copy SoD to Enhanced SoD**. 4. Click **OK**. 6. Sub-task: Set number sequence. 1. You can set number sequences for: After installing Security and Compliance Studio, generate the required number sequences first. Go to **Organization administration** > **Number sequences** > **Number sequences**. - **Risk ID**: Required to create risks. - **Request ID**: Recommended to create security requests. If you do not set a number sequence, you must manually enter a request ID when creating a security request. 2. In the **Area** field, select **Security and Compliance Studio**. > [!NOTE] > Note > > Initially, no number sequence is available for the **Security and compliance studio** area. 3. Reset the number sequences for the **Security and compliance studio** area to load the references for risks. This action loads both the **Risk ID** and **Request ID** references. Click **Manual cleanup**. 4. Click **Reset**. 5. Click **Yes**. 6. Now that the **Risk ID** and **Request ID** references are available for the **Security and compliance studio** area, generate the number sequence for each reference. The generated number sequences are automatically filled in the **Security and compliance studio parameters**. Click **Generate** and finish the wizard. 7. You can edit the generated number sequences in the **Security and compliance studio parameters** on the **Number sequences** tab. Go to **Default dashboard**. 8. Click **Security management**. 9. Click **Parameters**. 10. Click the **Number sequences tab**. 11. Click to follow the link in the **Number sequence code** field. 12. Close the page. 7. Sub-task: Set logging parameters. 1. Click the **Logs** tab. 2. You can clean up the security history audit log. If you do so, the retention period is required. For security reasons, you cannot set the retention period on the **Clean up audit log** dialog. Select the number of days for which you want to keep the audit log records. When you clean up the audit log, all audit log records that are older than the defined number of days, are deleted. In the **Audit log retention period (In days)** field, enter a number. 3. You can clean up the sensitive data audit log. If you do so, the retention period is required. For security reasons, you cannot set the retention period on the **Clean up sensitive data log** dialog. Select the number of days for which you want to keep the sensitive data log records. When you clean up the sensitive data log, all sensitive data log records that are older than the defined number of days, are deleted. In the **Sensitive data log retention period (In days)** field, enter a number. 4. You can apply continuous user logging. When enabled, for each user, this is logged: For each user, you can compare the accessed securable objects with the permitted entry points. To limit license costs, you can remove permissions for not-accessed entry points. See also: [Monitor user accessed securable objects](/data-management/docs/monitor-user-accessed-securable-objects) and [Analyze user role and license assignment](/data-management/docs/analyze-user-role-and-license-assignment). Select **Yes** in the **Enable continuous user logging** field. > [!NOTE] > Note > > To view the data logged, go to **Security and compliance** > **Inquiries** > **User continuous log**. - Accessed menu items and forms. - Access level: **Read**, **Write**, or **NA** (not applicable). - Operations performed on the accessed menu items and pages. 8. Close the page. ## Related - [Clean up security history audit log](/clean-up-security-history-audit-log.md) - [Clean up sensitive data log](/clean-up-sensitive-data-log.md) - [Security and compliance studio security roles](/security-and-compliance-studio-security-roles.md) - [Monitor user accessed securable objects](/monitor-user-accessed-securable-objects.md) - [Analyze user role and license assignment](/analyze-user-role-and-license-assignment.md)