Contact Open demo
Evidence

Show who decided what, and why

nerl0 maps its automated checks to ISO 27001, NIST CSF, CIS and NIS2, and shows what it can measure today, with counts and sources, not claims.

Open the demoRead the docs

Coverage over time, per framework

The share of each framework’s mapped checks that passed, among those measured. Not an assessment of compliance, and frameworks are not comparable with each other.

Evidence coverage
Evidence coverage over timeShare of each framework's mapped checks that passed, among those measured. Not an assessment of compliance; frameworks are not comparable with each other.
↗ Passing rate ⌄ScanDayWeek
0%10%20%30%40%50%60%11 Sep17 Sep23 Sep29 Sep05 Oct10 Oct16 Oct22 Oct28 Oct03 Nov14 Oct · scan 17NIS233%NIST CSF18%ISO 2700118%CIS6%
NowISO 2700121%NIST CSF24%NIS247%CIS8%

See what can be measured, area by area

Per framework and area of the company. Counts are always shown, and a dash says plainly that no check is mapped.

Frameworks and areas
By frameworkBy areaSources⌕⚙▥
Evidence coverage by areaShare of mapped checks that passed, among those measured.
HighMidLowNo mapped check
Area of the company
ISO 27001Annex A · 2022 · 10 of 93 mapped
NIST CSF2.0 · 4 of 106 mapped
CIS Controls8.1 · 2 of 153 mapped
NIS22022 · 6 of 42 mapped
Governance, policy & risk
–
50%1/2
–
67%2/3
People & HR
100%2/2
–
–
–
Assets & information
50%1/2
67%2/3
–
75%3/4
Identity & access
38%3/8 of 10
43%3/7 of 10
0%0/1 of 4
71%5/7
AI agents & non-human identities
–
–
100%1/1
33%2/6 of 12
Cryptography & secrets
–
–
–
0%0/1 of 2
Area of the company
Pass rate and checks measured
Framework and mapped controls
No mapped check, no claim

Counts, not claims

nerl0 covers technical evidence about AI agents and non-human identities only, a subset of each control.

01MappedA check is mapped to a framework control, or the cell says no mapped check.
02MeasuredCounts are always shown. One check can move a cell by a third or half.
03Not a verdictA candidate mapping of automated checks. Not an assessment of compliance.

Activity

Every event on this issue's paths, one lane per entity · newest first
ops-automation-agentDecisionDev Patel assigned an issue on ops-automation-agent
ops-automation-agentDecisionDev Patel opened an issue on ops-automation-agent
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent read prod/payments/stripe-key
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
nerl0Reproduced
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts

Who decided what, and why

Decisions, reads, writes and re-checks sit on one timeline per entity, so an auditor can follow the story without asking you.

  • DecisionsWho opened, assigned or closed an issue.
  • ActivityEvery read and write on the paths.
  • ReproducedEach path is re-checked on every scan.

Evidence is not what you say you did. It is what the next scan can still prove.

Evidencenerl0 · Show who decided what, and why

Questions.
Evidence.
Action.

See how nerl0 worksView docs →

Show your auditors the full story.

Open the demoTalk to us