Evidence that builds up
while you work
Carpent links what each module does to the measures NIS2, DORA, ENS and ISO 27001 require, and shows you what is covered and what is missing.
✓Included in the complete platform and available on its own
CAS-2317 · notification to INCIBE-CERT
Significant incident · detected 13 Oct at 23:47
Early warning
NIS2 art. 23 · 24 h6 h 12 min left
Incident notification
NIS2 art. 23 · 72 h2 d 6 h left
Final report
NIS2 art. 23 · 1 mes13 Nov
Draft prepared by the agent
Acme reports a significant incident in progress. Unauthorised access through SSL-VPN with stolen credentials and lateral movement to a purchasing application server. Suspected malicious act. No known cross-border effect. Containment in progress.
Report for the management body
October 2026 · generated 1 Nov
Status by framework · measures or controls
To decide this month
- Budget for MFA on the supplier VPN
- Laptop encryption policy (measure h)
- Annual training for management, required by Art. 20
- aRisk analysis and policies6 evidence itemsCovered
- bIncident handling14 evidence itemsCovered
- cContinuity and backups3 evidence itemsPartial
- dSupply chain4 evidence itemsPartial
- eVulnerability handling22 evidence itemsCovered
- fEffectiveness assessment5 evidence itemsCovered
- gCyber hygiene and training9 evidence itemsCovered
- hCryptography0 evidence itemsPending
- iAccess control and assets7 evidence itemsPartial
- jMFA and secure communications8 evidence itemsCovered
NIS2 notification
- Early warning · 24 h
- Notification · 72 h
- Final report · 1 month
Draft prepared from CAS-1042
NIS2, DORA, ENS and ISO 27001 ask for evidence. Carpent generates it from the platform's daily work, measure by measure, and prepares the notifications with their deadline from the case itself.
What it does
Early warning
24 h
Notification
72 h
Final report
1 month
Measure by measure
Each measure in Article 21 of NIS2, or each control of the standard you apply, with its status and its evidence.
Automatic evidence
Handled incidents, fixed vulnerabilities and completed training stand as evidence without gathering them by hand.
Reporting deadlines
The NIS2 24 hour, 72 hour and one month notifications are prepared from the incident case itself.
Board reports
A periodic compliance report for the management body, which NIS2 holds accountable.
In the console
Platform screens with data from Acme, the fictional company in the live demo.
CAS-2317 · notification to INCIBE-CERT
Significant incident · detected 13 Oct at 23:47
Early warning
NIS2 art. 23 · 24 h6 h 12 min left
Incident notification
NIS2 art. 23 · 72 h2 d 6 h left
Final report
NIS2 art. 23 · 1 mes13 Nov
Draft prepared by the agent
Acme reports a significant incident in progress. Unauthorised access through SSL-VPN with stolen credentials and lateral movement to a purchasing application server. Suspected malicious act. No known cross-border effect. Containment in progress.
Report for the management body
October 2026 · generated 1 Nov
Status by framework · measures or controls
To decide this month
- Budget for MFA on the supplier VPN
- Laptop encryption policy (measure h)
- Annual training for management, required by Art. 20
How it works
01Choose the framework
NIS2, DORA, ENS, ISO 27001 or PCI DSS. Carpent loads its measures and links them to the modules.
- ✓Measures of the chosen framework
- ✓Evidence from daily work
- ✓Gaps flagged
02Evidence is collected
The platform's daily work is stored as evidence for the measure it covers.
- NIS2 · Art. 21.bCovered
- NIS2 · Art. 21.hPending
- Early warning24 h
03Gaps are reviewed
Whatever the platform doesn't cover is flagged to resolve with your team or with Dasenda's.
Connected to the rest of the platform
It takes evidence from the Agentic SOC, Exposure management and Phishing simulation, without asking you for anything the platform already knows.
See the complete platform [ → ]Other modules

