This is the complete catalog of posture checks TigerGate runs against your cloud and SaaS accounts — 1,227 checks across 12 providers and 168 services. Pick a provider below to see every check ID, title, and severity. Use this index to:
  • Confirm coverage before connecting an account.
  • Look up the meaning of a check ID from a finding.
  • Build internal compliance maps (CIS / NIST / PCI / SOC 2 / HIPAA / ISO / GDPR / FedRAMP — every check is tagged with framework refs on its finding).

​
Major cloud providers

AWS

594 checks across 83 services — IAM, S3, EC2, RDS, EKS, Lambda, CloudTrail, KMS, GuardDuty, SecurityHub, and the long tail.

Azure

167 checks across 20 services — Entra ID, Storage, SQL, AKS, Key Vault, App Service, Defender for Cloud.

GCP

102 checks across 14 services — IAM, GCS, Cloud SQL, GKE, Compute, Cloud KMS, Cloud Logging.

Oracle Cloud (OCI)

51 checks across 13 services — IAM, Object Storage, Compute, VCN, Autonomous Database, OKE, Vault.

​
Kubernetes

Kubernetes

83 checks across the control plane (API server, etcd, controller manager, scheduler), worker nodes (kubelet), RBAC, pod security, and network policies.

​
SaaS & long-tail providers

Microsoft 365

101 checks — Entra ID, Defender, Exchange, SharePoint, Teams, Purview.

GitHub

24 checks — org settings, branch protection, app permissions, secrets.

Cloudflare

29 checks — account / zone security, DNSSEC, WAF, page rules.

OpenStack

34 checks — Keystone, Nova, Neutron, Cinder, Glance.

Vercel

26 checks — project, deployment, environment-variable, and domain security.

MongoDB Atlas

10 checks — cluster, network, encryption, MFA enforcement.

NHN Cloud

6 checks — Korean cloud provider — IAM and core infrastructure controls.

​
How check IDs work

Every check has a stable ID that follows the <service>_<descriptor> pattern, e.g. iam_inline_policy_no_administrative_privileges. Once a check fires in your account, that exact ID appears:
  • On the finding card in the dashboard.
  • In the audit log when the finding state changes.
  • In every export — CSV, JSON, HTML, PDF.
  • In the compliance scorecard PDF, alongside the framework controls it maps to.
Check IDs don’t change between TigerGate releases — if you’ve built a Jira automation against a specific ID, it stays stable.

​
Severity & compliance mapping

Each finding emits:
  • Severity — CRITICAL / HIGH / MEDIUM / LOW / INFO (filterable in the inbox).
  • Framework refs — CIS-3.0:1.20, NIST-800-53:AC-2, PCI-DSS-4.0:7.2.1, SOC2:CC6.1, HIPAA:164.312(a)(2)(i), ISO-27001:A.9.2.3, GDPR:Art-32, FedRAMP:AC-2, AWS-Well-Architected:SEC04, and more.
  • Resource ARN / ID — exact resource that failed.
  • Risk + remediation — written guidance and, where deterministic, a remediation snippet.
The compliance score on the dashboard is severity-weighted — see the scoring model on the overview.