The Diri control matrix is a visualisation of how the treatments (security controls) in your risk assessments are categorised and how far they are implemented. It is filled from the risk assessment and the treatment plan, and lets you drill down into the details. The control matrix makes it easy to see gaps in your controls, and to audit systems and organisations.
You find it on the risk assessment dashboard, below the registration and assessment process. It is also available as the Control Matrix widget for dashboards and reports.
The matrix shows four kinds of information:
Use Expand table to see the rows, and the framework filter to measure the controls against a specific standard such as ISO 27001 or NIS2. The framework filter uses the treatments' control tags.
The summary view is shown first, as illustrated above. Even this view gives useful information. Ø means that the square has no treatments. In the example there is one control to Identify, but none implemented or planned in this class. Only 6 of 31 protection measures are in place (green in the pie chart), while several are planned (orange) or ongoing (yellow). Only one Detect measure is in place, while one is planned and another proposed. Respond and recover is read the same way. In total, 8 of 41 measures are in place for this system.
Expand the matrix to see more. The fully expanded matrix holds a lot of information, but is a handy tool for finding gaps in the chain of controls:
An interpretation of the matrix above:
All treatments in the example have been categorised, so the Uncategorized squares are empty. In the Identify class there is one administrative control. Using Diri for risk assessments is itself an identifying control, and could be added both as a technological control and as an administrative routine.
The Protect and maintain class has 31 controls, but only 6 are implemented. The need for physical controls depends on location and hosting. Self-hosted systems need to be secured at the right level, while the service provider often meets the physical security requirements for a cloud application. Still, those requirements should be written into the contract.
Technological controls are typically associated with cybersecurity, but many of them need an Administrative control as well, such as a routine for appropriate use. A typical example is plenty of technological detection controls, such as logging and monitoring, but no administrative routine to actually analyse the logs.
Click a square in the matrix to drill down:
Click a treatment in the details to open it for viewing and editing. A treatment that lists several causes or consequences reduces risk for all of them.
We have only scratched the surface of the control matrix, and you may find even better ways of using it.
One good use is as a compliance tool for the organisational risk assessment. If you manage several organisations or units and want all of them to assess a standard set of risks and controls, create a template or copy an assessment to reuse the control set in each sub-organisation. Combined with the control matrix, this gives you an excellent tool for auditing and tracking progress in the overall security work.
The same approach works for IT systems, and the control matrix also works for auditing a single system, as shown above. It immediately highlights missing controls and missing implementation.