01
Five live connectors
AWS, GitHub, Google Workspace, Okta and PostgreSQL. AWS checks IAM and MFA settings, S3 encryption and CloudTrail configuration. GitHub checks branch protection and required reviews.
Evidence collection
Evidence that collects itself.
Read-only connectors pull configuration evidence from your cloud, identity and code tools. Documents without an API are uploaded once and go through the same review.
The job
From scattered files to one place
Today
Evidence is a folder of screenshots, log exports and emailed PDFs, assembled in the weeks before an audit. Some of it is already out of date when it is collected.
In CyberPlug
Connectors take a configuration snapshot every 24 hours. Checks run against the stored snapshot, and each result is linked to the controls it proves. A person reviews what needs a person.
Capabilities
What it does
02
Configuration, never content
A connector reads whether encryption is on. It does not read the encrypted data, your users' email, your source code or your customer records.
03
Read-only by design
Every connector requests the narrowest scope that satisfies its checks. None can change your configuration.
04
Fresh by default, and honest when stale
Snapshots run every 24 hours and on demand after you fix something. A failed run marks the connector stale instead of quietly using old data.
05
Reproducible results
Checks run as pure functions over the stored snapshot, so a provider outage cannot fail a control and a result can be replayed.
06
Documents get the same review
Board minutes, signed policies and training records are uploaded, checked for structure and approved by a person. Each carries a validity period, so an old policy does not keep a control green.
How it connects
Part of one platform
- Evidence is linked to the controls in Compliance management.
- Its freshness feeds the readiness score in Audit readiness.
- Evidence moves through needs artefact, pending review, active, expiring and expired, so the dashboard shows what is about to lapse.
Who uses it. Administrators and technical leads connect systems once. Compliance Officers review evidence. Auditors inspect it.
Frameworks it serves
Works across the frameworks you answer to
FAQ
Questions we hear most
What permissions do connectors need?
The narrowest read-only scope that satisfies the checks. Where a provider offers a security-reader or audit role, we ask for that.
How are credentials stored?
Connector secrets are encrypted before they reach the database and are never displayed back in the interface.
Do you have a connector for our tool?
Connector coverage is driven by customer demand. Request one through the support portal with the provider, the controls it should satisfy and the scope your security team would grant.
Is customer evidence used to train AI models?
No. Evidence documents are never used to train public models.