Solutions

Security compliance software

Compliance in SecBoard is the record of which requirement applies, which control covers it, and whether the evidence is there. It is not a certificate.

Demo Price Contact

Frameworks and local rules

A company instance can follow PCI DSS, ISO 27001, SOC 2, HIPAA, GDPR, or an internal policy set. Local compliance holds regulator-specific requirements. The standards module stores the PCI DSS requirement text and the ISO/IEC 27002 controls, with translations and AI-powered search over that catalog.

Evidence without a separate spreadsheet

Framework compliance maps controls, attaches evidence, and tracks status. Mandatory processes remind the owner and record that the step was confirmed. Related work stays in the same product: assets, access, incidents, policies, training, and vendors. For Ukrainian banking rules, the knowledge base already explains NBU regulations 143, 123, 95, and 67.

Questions

No. It keeps the framework, the control status, and the evidence. The certification decision stays with the auditor or the regulator.

Yes. The compliance module uses company-specific instances and templates, including internal policies next to the external frameworks.

In the knowledge base articles on NBU regulations 143, 123, 95, and 67. They explain the regulation; they are not a second compliance module.

The compliance module page lists what the function does. This page is the job: keep security compliance evidence in one place.

Related