What is a security measure?
Software, processes, teams that secure a perimeter. It is the central element of Tenacy linking objects together.
The measure can be:
Implemented: already in place in your organization
Not-implemented: does not exist in your organization, and you need to implement it
Private measures or with beneficiaries
Depending on how your organization operates, some security measures may be maintained by a single perimeter and shared with others, while other security measures may be implemented independently by each perimeter.
Private measures
For a chosen policy, each perimeter will have:
Its own measure (derived from the same proposed measure)
Its own recurring tasks
Collect its own metrics
In the example below, Lyon and Lille will each operate their measure, collect their recurring tasks and metrics independently.
Offered measures
1. Offered measures, centrally measure
For a chosen policy:
Only one measure is created for multiple perimeters
One of the perimeters is responsible for operating it for itself (or not) and the others
Only one metric will be collected for different perimeters
🔎 It is entirely possible for a perimeter to offer the operated measure to other perimeters without implementing it for itself.
In the example below, Belgium will be in charge of implementing the measure and collecting recurring tasks and metrics for the perimeters of Germany, Lille and Lyon.
2. Offered measure and locally measured
Nuance on the offered measure, it is also possible to choose to collect metrics locally for each perimeter.
Taking the previous example, the "Collect metrics for each perimeter" box is checked, so metrics will be collected for each of the 3 perimeters.
🔎 For collection, either each perimeter collects on its own, or Lyon can still be responsible for collecting both metrics.
💡 To find out how to share a measure to other perimeters, you can read this article