Skip to content
ISO/IEC 27001:2022

Annex A evidence.Generated, not gathered

Stop assembling screenshots for the auditor. PollySec collects technical evidence automatically, all year, and maps it to the five Annex A controls it can honestly evidence, in a report you generate in one click.

The reports

Annex A

Five controls.No padding

The ISO/IEC 27001:2022 Evidence Report maps PollySec's technical findings to the Annex A controls they can honestly evidence, and says where the evidence stops.

A.5.7

Threat intelligence

Findings flagged when their CVE is known to be exploited in the wild.

A.5.9

Inventory of information and other associated assets

Discovered domains, subdomains, certificates, networks and hosts, with status and last-seen dates.

A.8.8

Management of technical vulnerabilities

Vulnerabilities found, ranked, checked and tracked to closure.

A.8.20

Networks security

Reachable ports and services per asset, with product and version where a banner names them.

A.8.24

Use of cryptography

Certificates on reachable endpoints: issuer, validity and self-signed state.

Evidence toward selected Annex A controls. Not a certification, and not a replacement for your ISMS.

Between audits

Keep the evidencerunning

Certification is a moment. Your attack surface changes every week. PollySec keeps the evidence current, so the next report is one click away.

Automatic

Outside and inside, re-checked automatically all year.

Checked

Serious findings are tested live where a test can settle them. A wrong one is withdrawn, never counted as fixed.

NIS2 too

The same data, mapped to NIS2 Article 21(2), plus a trust link you can send a customer.

NIS2 evidence

Show the auditor what you fixed.And when

We'll generate the ISO 27001 report on a real surface with you.

Book a demo