You classify each piece of information once, and Ariadne ISMS automatically passes the result on to every process and system that handles it. You don't have to rate each system separately, and your required protection stays traceable in the audit.
Prerequisites
- Classifications are part of managing a record. You are the Owner of the information or have the Key User or Admin role.
- As a Stakeholder, you can edit the information but not classify it.
- The information already exists, for example because you created it on a business process.
Two classifications, two questions
Each piece of information has two separate classifications. You need both for the information to count as fully classified.
Security classification
Confidentiality and integrity
You rate confidentiality and integrity, each on one level of the impact scale, and give one shared rationale. This determines the required protection of processes and assets.
Guiding questions
- Confidentiality: Who may this information reach, and how much damage is done if it goes beyond that group?
- Integrity: How much damage is done if this information is manipulated or it is unclear how a change came about?
Privacy classification
Personal data under GDPR
You record whether the information contains personal data and whether special categories are involved. This shows at a glance which processes and systems are relevant for data protection.
Guiding question
- Whose rights are affected if something goes wrong with this information?
Rate confidentiality and integrity
- Open Information and select the information you want to classify.
- Click the edit icon next to Security classification.
- Choose a level under Confidentiality level and Integrity level.
- Explain your rating under Rationale (optional). The rationale applies to both values.
- Save the classification.
The levels of the impact scale
By default, Ariadne ISMS uses five levels. Levels and descriptions may differ in your organization. Only Ariadne Support can change them.
| Value | Level | Description |
|---|---|---|
| 1 | Negligible | No significant damage |
| 2 | Low | Minor damage, manageable in regular operations |
| 3 | Medium | Noticeable damage, manageable with management effort |
| 4 | Severe | Serious damage with considerable consequences |
| 5 | Catastrophic | Catastrophic damage, the company's survival is at risk |
Record data protection
- In the information, click the edit icon next to Privacy classification.
- Select the applicable options from the table below.
- Explain your choice under Add rationale (optional) if needed, and save.
| Option | Meaning |
|---|---|
| Personal data | General personal data under GDPR |
| Special categories (Art. 9) | Sensitive data such as health data or religious beliefs |
| Criminal data (Art. 10) | Data on criminal convictions and offenses |
Keep track of reassessments
Reassessment
When the next classification is due
The ISMS schedules the next classification by itself. The more critical the information, the sooner it is due again. The Reassessment field shows when, for example "In 90 days".
How the due date is calculated
- New information: first due after 90 days.
- After classification, the higher value of confidentiality and integrity counts (see table).
- The privacy classification does not affect the due date.
| Highest value of C and I | Reassessment after (default) |
|---|---|
| Catastrophic | 90 days |
| Severe | 180 days |
| Medium | 365 days |
| Low, Negligible | 730 days |
Your admin sets the intervals under Settings > Information classification. They may differ from the defaults in your organization.
When information counts as done
On the dashboard, information counts as Assessed when both the security and the privacy classification exist and the reassessment is not overdue. If a classification is missing, it appears under Action required as "Assess". If the reassessment is due, it shows "Reassess".
What your classification affects
| 1 Information You rate C, I and data protection once. | 2 Business process Takes the highest value of all linked information. | 3 Asset Inherits the required protection through the dependencies that handle the information. |
Under Business processes in the information, you see which processes handle it. When your classification changes, the ISMS recalculates processes and assets automatically.
Related articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article