When you use a public policy from the catalog, all of its requirements are factored into your compliance score. However, depending on your organizational context, some of these requirements may not be applicable.
To do this, you have two options: either directly delete the requirements that are not related to your organizational context, or mark them as non-applicable in order to hide them and exclude them from your score.
Delete the requirements that are not applicable to your organizational context
Create a Private Copy of the Public Policy
Click the gear icon at the top of the screen.
Go to the Catalog.
Search for the desired policy
Without clicking on the policy, simply hover your cursor over the row.
At the end of the row, click “Create a copy”
During the copy process, choose the attachment in your organization for the policy (e.g., to the Root).
🔎 This attachment does not mean the policy will automatically apply to all perimeters. It only defines which entities in your structure will have access to the policy.
💡 Creating a copy of a public policy consumes one token, but only once per policy.
If you’ve already instantiated the public version :
Copying it won’t consume another token.
You can create as many private copies as needed if your organization operates in different contexts.
Edit Your Private Version
Once the copy is created:
You’ll find it in the Catalog, labeled as "Private".
Click on the private policy to open it.
Navigate through the sections or requirements, then select the ones you want to remove.
Click the "Delete selected elements" button at the top of the policy.
💡 If an entire section of the policy doesn’t apply to your context, you can delete it completely by selecting the group’s checkbox—this will automatically select all the requirements it contains.
🔎What If You Deleted a Requirement or Section by Mistake?
You have two options:
Option 1: Manually add back the missing element
Click “Create a group” if you want to add a new section.
Or click “Add requirement” to re-add a specific requirement inside an existing group.
Option 2: Start over with a new copy
Delete the incorrect private version.
Create a new copy of the public policy.
This time, only remove the appropriate elements.
Link the Private Policy to the Relevant Perimeters
Go to the Policies section.
In the Perimeters column, click to assign the perimeters that should be evaluated under this policy.
🔎 Any security measures already in place within these perimeters will be automatically taken into account in the evaluation.
There’s no need to manually re-link them—Tenacy handles this for you!
💡Can I Still Edit My Policy After Linking Perimeters?
Yes, you can:
Edit the policy directly from the Catalog, or
From the Policies section, by clicking on “Edit policy”.
Declare certain requirements as non-applicable to your context
Create a Private Copy of the Public Policy
Click the gear icon at the top of the screen.
Go to the Catalog.
Search for the desired policy
Without clicking on the policy, simply hover your cursor over the row.
At the end of the row, click “Create a copy”
When making the copy, choose the attachment in your organization for this policy (for example, at the root) and replace the existing priority scale with the one called « Applicability »
🔎 This attachment does not mean the policy will automatically apply to all perimeters. It only defines which entities in your structure will have access to the policy.
💡 Creating a copy of a public policy consumes one token, but only once per policy.
If you’ve already instantiated the public version :
Copying it won’t consume another token.
You can create as many private copies as needed if your organization operates in different contexts.
Edit your private version
Once the copy is created:
You will find it in the Catalog, under the label « Private ».
Click on this version to open it.
Browse through the different requirements. For each one, you want to set as non-applicable:
Click on the Edit icon,
Select the priority « Non-applicable »
Associate your private policy with the relevant scopes
Once your requirements have been adjusted:
Go to the Policies section.
In the perimeters' column, click to add the scopes that should be assessed according to this policy.
After adding a scope, apply the priority filter on « Applicable ».
👉 From that point on, you will only see the requirements that are applicable to your context.
🔎 Any security measures already in place within these perimeters will be automatically taken into account in the evaluation.
There’s no need to manually re-link them—Tenacy handles this for you!
💡Can I Still Edit My Policy After Linking Perimeters?
Yes, you can:
Edit the policy directly from the Catalog, or
From the Policies section, by clicking on “Edit policy”.
👉 If you have several entities with different applicability of the requirements, feel free to repeat the process and create as many copies as needed.
If you have any questions or need help adapting your policies, feel free to contact our support team.