Skip to main content

Use the properties of a perimeter

Learn how to create perimeter properties, apply them to your perimeters and use them to filter and report in your dashboards.

Properties enrich the identity card of your perimeters. They let you associate additional information with each perimeter (operating system types, recertification date, CIAP level, inclusion in a certification scope), then use it as filtering and reporting criteria. A property is defined once, then applied to as many perimeters as needed.

💡 Properties are global for a given context: once created, a property is available across all perimeters of that context.

Create a property

Go to the cog wheel ⚙️ then to the Properties menu, and click Add value. You then define the property's type, its visibility, its data entry rules and, if needed, the perimeter type it applies to.

💡 You must be a global pilot to define properties from the cog wheel.

properties - en

Two fields describe the property:

  • Name: the property's label as it appears on the perimeters' identity card.

  • Description: a help text explaining the expected value. It is displayed when entering the value on a perimeter.

Choose the property type

The type determines the nature of the value you will be able to enter on each perimeter. The available types are:

  • Single choice: a single value to select from a predefined list

  • Multiple choice: several values to select from a predefined list

  • Integer value: a whole number

  • Text: free text entry

  • Date: a date

  • Domain: a domain name (for example test.acme.com)

  • URL: a link

  • Flag: an indicator turned on or off (on / off)

  • Subnet: a range of network addresses (for example 10.0.0.0/24)

  • Scale: a value on a scale

Set visibility and data entry

For each property, you choose who can see its values and who can modify them.

Visibility: it controls who can view the property's values.

  • Restricted: only global pilots see the property's values.

  • Unrestricted: any pilot with access to a perimeter sees the value of that perimeter.

Data entry: it controls who can fill in or modify the property's values.

  • Root: only global pilots can enter the values.

  • Local: any pilot with access to a perimeter can enter the value of that perimeter.

⚠️ Data entry for a property can be made mandatory. In that case, a perimeter whose value is not filled in appears as an anomaly: a yellow dot is displayed on its identity card in the Organization module, prompting you to fill in the value.

Limit a property to a perimeter type

You can associate a property with a single perimeter type only (internal, supplier or application) when it is only relevant for that type. A property associated with the supplier type, for example, will only be visible on supplier perimeters.

Examples of property use

  • Reporting criterion: filter only the perimeters identified as certified.

  • Cyber environment mapping: list the operating system types used on a perimeter.

  • Tracking information: record a recertification date.

  • Expected security level: indicate the CIAP level (Confidentiality, Integrity, Availability, Proof) of a perimeter.

💡 If you have set up accumulators in your questionnaires, Tenacy automatically creates the corresponding properties when answers are submitted. These properties cannot be modified and let you report on the basis of questionnaire answers. They appear by checking "Show all" on the perimeter's identity card.


Apply a property to your perimeters

Value entry is done in the Organization module, from a perimeter's identity card. Place the cursor on the relevant perimeter, open its identity card, then go to the Properties tab to fill in or modify the values.

🔎 To fill in the properties of many perimeters in a single operation, see: Import and export perimeter properties and contacts.


Manage and edit a property

The property list, under the cog wheel ⚙️ > Properties, is only accessible to global pilots. Any change made to a property is immediately reflected on the identity cards of all relevant perimeters.

⚠️ Some operations cause data loss:

  • Deleting a property removes it from all identity cards and permanently deletes the values associated with it.

  • Deleting a choice from a list (single or multiple choice type) empties the corresponding value on all perimeters where that choice was set.


Use properties in your reporting

Properties can be used in dashboards in two ways: by displaying their values, or by filtering the perimeters retained in a block.

Display a property's values in a dashboard

Open the Dashboards module, then the Dashboards tab, and edit the desired dashboard. Add a block, choose Perimeters and grouping then A grouping, select your grouping or the root, open the Properties tab and select the property to display. The block then presents the values of that property for the relevant perimeters.

Filter a dashboard block on a property

You can restrict the perimeters taken into account in a block to only those meeting a property criterion. This gives you, for example, a compliance score calculated only on the perimeters within a certification scope. This is done in two steps.

Step 1: create a filter. In the Organization module, open the Advanced filter (via the magnifier), click Add property to define your property criterion, then save the filter.

Step 2: apply the filter to a block. Edit the desired dashboard block and select your filter in the Properties filter field. Only the perimeters matching the filter are now retained in the block.

💡 Filtering by property is a lightweight alternative to creating a secondary tree: rather than recreating a dedicated grouping (for example an ISO grouping), you mark the relevant perimeters with a flag and filter on it.


Frequently asked questions

Who can see and modify a property's values?
It depends on the property's settings. Restricted visibility reserves viewing for global pilots, whereas unrestricted visibility opens it to any pilot with access to the perimeter. Likewise, "root" data entry reserves modification for global pilots, whereas "local" data entry allows it for any pilot with access to the perimeter.

Can a property concern only one perimeter type?
Yes. When creating it, you can restrict a property to a single perimeter type (internal, supplier or application). It will then only be visible and fillable on perimeters of that type.

What happens if a mandatory property is not filled in?
The relevant perimeter appears as an anomaly in the Organization module, marked by a yellow dot on its identity card, which lets you quickly identify missing values.

What happens if I delete a property or a list choice?
Deleting a property removes it from all identity cards and permanently deletes the associated values. Deleting a choice from a list empties the corresponding value on the perimeters where it was set. These actions are irreversible.

Can I fill in the properties of several perimeters at once?
Yes, via the import feature of the Organization module. It lets you update the properties and contacts of many perimeters from a file, without modifying them one by one.

Did this answer your question?