Which frameworks does blacklens.io support?

blacklens.io provides technical evidence for NIS2 (Directive (EU) 2022/2555) for essential and important entities, DORA (Regulation (EU) 2022/2554) for financial entities and their ICT providers, ISO/IEC 27001:2022 with Annex A controls such as A.5.7, A.8.8 and A.8.16, TISAX based on the VDA ISA, and the critical infrastructure (KRITIS) duty to demonstrate the state of the art. Cyber insurers' questionnaires on MFA, patch management, exposed services and the external attack surface can also be answered with current data instead of estimates.

Is blacklens.io a GRC or ISMS tool?

No. blacklens.io is the technical data source your management system relies on: inventory, vulnerabilities, threats, supply chain and reports. Policies, risk registers and action plans stay in your ISMS or GRC system. You transfer the evidence there via CSV export, scheduled reports and the REST API. blacklens.io does not replace legal advice.

Which reports are suitable for an audit?

The executive report for management, the vulnerability report for the technical review, the pentest report for manually verified findings and the query report, which turns any BQL query into a PDF. All of them can be sent automatically daily, weekly or monthly by email. For evidence beyond the reports, you can export any list as CSV, extended CSV or PDF.

Is blacklens.io alone enough for NIS2 compliance?

No. NIS2 also requires organisational measures such as policies, training, a reporting procedure and management involvement. blacklens.io provides the technical evidence for vulnerability handling, asset inventory, supply chain monitoring and threat intelligence, the part that cannot be proven continuously without a tool. The organisational measures remain the job of your management system.

How long does evidence remain available?

Closed findings are archived 30 days after closure and not deleted; nightly statistics snapshots preserve the exposure score history. For long-term retention we recommend scheduled PDF reports that you keep in your document management system. That way you can still prove when which vulnerability was detected, assessed and closed.

Does blacklens.io also support TISAX?

Yes, indirectly. TISAX is based on the VDA ISA, whose technical questions on vulnerability management, network security, cloud and suppliers can be answered with the same evidence as the ISO 27001 Annex A controls. An official TISAX label is issued only by an accredited audit provider. blacklens.io provides the technical proof you present in the assessment.

How can you trace who changed what?

Through the activity log: an audit log with deep links shows who changed what and when. You control access with 8 roles, custom roles and 50 permissions, and sign-in runs via SSO with Microsoft Entra ID or Google and MFA. Together with status, comments, timestamps and retest results on each finding, this creates a traceable record for auditors.

Solutions

Compliance & audit: evidence that stays current

Compliance means being able to prove security. blacklens.io generates the technical evidence for NIS2, ISO 27001, TISAX and DORA continuously: inventory, vulnerabilities, remediation and reports.

Start free trial Book a demo

Evidence for auditors and insurersas PDF

Asset inventoryISO/IEC 27001 A.5.9continuous

Vulnerability reportISO/IEC 27001 A.8.8, TISAXmonthly

Threat Center matchingISO/IEC 27001 A.5.7real time

Vulnerability handlingNIS2 Art. 21 (2) econtinuous

Supplier watchlistNIS2 Art. 21 (2) dcontinuous

Where implementation fails in practice

Stale inventory

The asset inventory is maintained for the audit and goes stale afterwards. New cloud resources are missing.

Measures that are hard to prove

"We patch regularly" is not evidence. Auditors want to see what was closed and when.

No current threat data

Whether a new critical CVE affects your own systems is researched manually, if at all.

High manual effort

Asset lists and reports are kept in spreadsheets and reworked before every audit.

How blacklens.io generates compliance evidence

Evidence is produced during everyday operations, not in the week before the audit.

Newly discovered assets+4 since yesterday

beispiel-gmbh.atRoot domain

vpn.beispiel-gmbh.atFortiGate SSL-VPN 7.0.12Critical

dev-old.beispiel-gmbh.atGitLab 15.2Shadow ITHigh

mail.beispiel-gmbh.atExchange Server 2019Medium

203.0.113.24OpenSSH 8.9NewInfo

Remediationone workflow for every source

12Open

5In progress

2Risk accepted

48Closed

CVE-2024-21762

Assigned to IT operations
Update installed
Re-scan confirmed: closed automatically

Early warning47 min ago

CVE-2024-21762FortiOS SSL-VPNCritical

CVE published08:12
2 assets in your inventory affected09:00
Confirmed by PoC scan09:26
Alert sent to Microsoft Teams09:27

Supplier watchlist12 suppliers

Logistik Partner GmbHListed on a ransomware leak site, 30 min agoCritical

Software Zulieferer AGSoftwareNo hits

Muster SteuerberatungTax advisoryNo hits

Reportsscheduled by email

PDFExecutive reportWeekly, Monday 07:00

PDFVulnerability reportMonthly

PDFPentest reportAfter every test

Management, head of IT

Visuals show sample data.

Frameworks at a glance

NIS2

Article 21 requires vulnerability handling, supply chain security and incident handling, among others.

DORA

ICT risk management, third-party risk and resilience testing for financial entities and ICT providers.

ISO/IEC 27001:2022

Continuous evidence for Annex A controls such as A.5.7, A.8.8 and A.8.16.

TISAX

Answer the VDA ISA questions on vulnerabilities, network and suppliers with the same evidence.

Critical infrastructure (KRITIS)

Demonstrate the state of the art with continuous monitoring of the external and internal attack surface.

Cyber insurance

Answer questions on MFA, patches and exposed services with data instead of estimates.

Example from practice

Critical infrastructure operator prepares for a NIS2 audit

A critical infrastructure company had to implement NIS2 technically and prove it in an audit. With blacklens.io, attack surface and vulnerabilities were monitored continuously, prioritised and documented with clear ownership.

Result
Technical protection of the external systems rated "exemplary and consistently documented" in the audit.

Progresslast 90 days

Critical findings143

Exposed services3821

Visuals show sample data.

Frequently asked questions

: blacklens.io provides technical evidence for NIS2 (Directive (EU) 2022/2555) for essential and important entities, DORA (Regulation (EU) 2022/2554) for financial entities and their ICT providers, ISO/IEC 27001:2022 with Annex A controls such as A.5.7, A.8.8 and A.8.16, TISAX based on the VDA ISA, and the critical infrastructure (KRITIS) duty to demonstrate the state of the art. Cyber insurers' questionnaires on MFA, patch management, exposed services and the external attack surface can also be answered with current data instead of estimates.
: No. blacklens.io is the technical data source your management system relies on: inventory, vulnerabilities, threats, supply chain and reports. Policies, risk registers and action plans stay in your ISMS or GRC system. You transfer the evidence there via CSV export, scheduled reports and the REST API. blacklens.io does not replace legal advice.
: The executive report for management, the vulnerability report for the technical review, the pentest report for manually verified findings and the query report, which turns any BQL query into a PDF. All of them can be sent automatically daily, weekly or monthly by email. For evidence beyond the reports, you can export any list as CSV, extended CSV or PDF.
: No. NIS2 also requires organisational measures such as policies, training, a reporting procedure and management involvement. blacklens.io provides the technical evidence for vulnerability handling, asset inventory, supply chain monitoring and threat intelligence, the part that cannot be proven continuously without a tool. The organisational measures remain the job of your management system.
: Closed findings are archived 30 days after closure and not deleted; nightly statistics snapshots preserve the exposure score history. For long-term retention we recommend scheduled PDF reports that you keep in your document management system. That way you can still prove when which vulnerability was detected, assessed and closed.
: Yes, indirectly. TISAX is based on the VDA ISA, whose technical questions on vulnerability management, network security, cloud and suppliers can be answered with the same evidence as the ISO 27001 Annex A controls. An official TISAX label is issued only by an accredited audit provider. blacklens.io provides the technical proof you present in the assessment.
: Through the activity log: an audit log with deep links shows who changed what and when. You control access with 8 roles, custom roles and 50 permissions, and sign-in runs via SSO with Microsoft Entra ID or Google and MFA. Together with status, comments, timestamps and retest results on each finding, this creates a traceable record for auditors.

CTEM

The cycle that generates the evidence continuously.

Unified Vulnerability Management

One process for external, internal and cloud vulnerabilities.

Supply chain monitoring

Match your suppliers against ransomware leak sites continuously.

Evidence that is ready before the next audit

Start with your domains and see how inventory, findings and reports come together.

Try free for 14 days Book a demo

14 days free, all features
No credit card required
We walk you through your first findings