Book a demo
Integrations & automated evidence

Evidence that collects itself.

Connect cloud, code, identity, HR, device and IoT systems. CompliLens checks them every day against 132 rules mapped to real controls, and drafts what needs fixing for a person to review.

Book a demo Watch the tour
Evidence feed · todayLive
S3 buckets block public accessISO 8.3 · CC6.1
Passing
Branch protection on mainISO 8.32 · CC8.1
NCR drafted
MFA enrolled for all usersISO 5.17
Passing
Disk encryption on 212 devicesISO 8.24
Passing
Cold room 2 at 9.4°CISO 9001 8.7
Incident drafted
Defender for Cloud enabledISO 8.16 · CC7.2
Passing
18connector types
132rules
Dailychecks
Connector explorer

Pick a connector to see what it checks

Integrations (Connectors, Rules & Feeds)

From signal to fix, with a person in the loop

Secure links to your other tools so CompliLens can check settings and gather evidence by itself.

How it works
  1. Open Integrations → Connectors → Add Connector. Choose a tool from the list: GitHub, GitLab, Bitbucket, AWS, Azure, Google Cloud, IBM Cloud, Oracle Cloud, DigitalOcean, Tencent Cloud, Sify Cloud, BambooHR, Okta, Microsoft Intune, Particle, AWS IoT SiteWise, plus Jira and Slack for sending messages out.
  2. Enter the credentials, which are stored encrypted. Click Test connection.
  3. CompliLens syncs daily (or on demand) and runs more than 130 rules. Examples: "Is two-factor required?", "Are storage buckets private?", "Is branch protection on?", "Did a cold-storage sensor go out of range?"
  4. Results appear in the Evidence Feed as compliant or non-compliant findings, each tied to real ISO 27001 / SOC 2 controls.
  5. Serious findings become drafts in the NCR Feed (control gaps) or Incident Feed (real events like a temperature excursion). A person reviews and clicks Accept, Dismiss or Snooze. Nothing is created without a human decision.
  6. The Rules tab lets you switch rules on or off and decide which ones create drafts.
  7. The Overview tab highlights unhealthy connectors, open findings by source, recent findings and pending drafts, and it scales to large numbers of connectors.
Example
Okta shows three admin accounts without two-factor. A draft NCR appears; the security manager accepts it, assigns an owner, and the fix is tracked to completion.
Rule catalog

Every rule names the control it proves

app / integrations / rules
RuleSourceSeverityControlsEscalates to
AWS-003 S3 buckets block public accessAWSCriticalISO 8.3 CC6.1NCR
GH-001 Branch protection on default branchGitHubHighISO 8.32 CC8.1NCR
OKTA-002 MFA for all active usersOktaHighISO 5.17NCR
PRT-001 Cold storage temperature excursionParticleCriticalISO 9001 8.7Incident
INT-004 Antivirus enabledIntuneMediumISO 8.7Queue only

Connectors use real platform APIs. Not every rule in the catalog has a live check for every connector yet.

Cold storage

Temperature excursion

9.4°C against an 8°C limit drafts an incident mapped to ISO 9001 8.7.

Power plant

Vibration out of range

5.1 mm/s against a 4.5 mm/s ceiling, plus calibration-overdue checks.

Delivery

Jira and Slack

Accepted NCRs open Jira issues. Evidence requests post to Slack.