AiVRIC Platform Guide
AiVRIC.com Trust Center Support Insider Access
⌘K
Onboarding

Getting started

Launch AiVRIC quickly with a secure baseline. Follow the four-step flow below, then connect your first cloud account.

1

Plan workspaces

Map environments to workspaces (e.g., prod, staging, R&D). Align each with data sensitivity and named owners.

  • Define owners in IAM groups before inviting users.
  • Enable SSO and SCIM first to enforce directory-driven access.
2

Secure access

Use SSO + MFA; grant least-privilege roles in cloud accounts. Configure break-glass with short-lived tokens.

  • Map cloud roles to AiVRIC permission groups.
  • Audit login attempts weekly; alert on anomalies.
3

Connect systems

Connect cloud accounts, Kubernetes clusters, GitHub, and ticketing to start continuous control monitoring.

  • Use deployment templates provided per connector.
  • Verify data collection scope before enabling enforcement.
4

Apply guardrails

Enable policy packs for compliance (SOC 2, ISO 27001) and AI safeguards (PII, secrets, jailbreaks).

  • Run dry-runs first; review impact report before enforcing.
  • Promote to enforce mode after stakeholder sign-off.
CloudSignals — Overview Expand CloudSignals Command Center dashboard showing posture threat score, active findings breakdown, threat map, and control plane activity
Your command center after onboarding — threat score, live findings by severity, threat map, and posture control plane are all populated once your first connector is active and a scan completes.

Connect your environment

All connectors are powered by CloudSignals+RiskOps™ — AiVRIC's continuous posture monitoring engine. Every connected provider is audited automatically on a 24-hour cycle.

ProviderPurposeQuick action
AWSMonitor IAM hygiene, network rules, and resource configurations for drift.Deploy read-only IAM role via CloudFormation Quick Link.
Microsoft AzureAudit subscriptions for misconfigurations, identity posture, and policy compliance.Create App Registration + Service Principal; enter Tenant ID, Client ID, Secret.
Google Cloud PlatformScan GCP projects for posture drift and framework control gaps.Create read-only Service Account; paste JSON key into AiVRIC.
KubernetesSecure cluster workloads, service account access, and runtime configurations.Paste kubeconfig; apply read-only RBAC manifests.
GitHubProtect repos, branch protections, secrets exposure, and pipeline tokens.Connect via PAT, OAuth App, or GitHub App.
Microsoft 365Monitor tenant controls for SOC 2, PCI DSS, and CMMC compliance.Register Entra ID app; configure certificate authentication.
MongoDB AtlasAudit database cluster configurations and access controls.Generate an Atlas API key pair and paste into AiVRIC.
Alibaba CloudMonitor resource configurations and IAM posture for drift.Use RAM Role Assumption or static credentials.
Jira / ServiceNowSend findings to owners and track remediation bidirectionally.Connect via OAuth; map severity to ticket priority.
/assets Expand CloudSignals All Assets view showing 319 discovered resources with sync status, ownership coverage, and criticality filters
Asset inventory populates automatically after the first scan — every discovered resource is listed with ownership, criticality, and last-sync status.
/scans Expand CloudSignals Scans page showing scan history with provider, status, duration, and findings count per scan
Scan history — every audit run is logged with provider, status, duration, and finding counts. On-demand scans run alongside the 24-hour scheduled cadence.
Full connector guides — step-by-step instructions and authentication details for every provider — are on the Connectors page.

Collaborate and ship

  • Approvals: Require dual approval for high-impact guardrails; log who approved and when.
  • Change windows: Align policy changes with your release calendar.
  • Notifications: Route critical findings to Slack/Teams with runbooks attached.
  • Observability: Forward audit logs to your SIEM; tag events by workspace.
  • Testing: Validate connectors in staging workspaces before production.
  • Ownership: Keep owners visible in tickets for fast escalation.

Resources

Connector setup guides

Step-by-step instructions for all eight supported cloud providers.

View all connectors

CloudSignals+RiskOps overview

Scan cadence, compliance mapping, alerts, SIEM integration, and reporting.

Read the overview

Trust Center

SOC 2 readiness, penetration testing summaries, and data handling details.

Open Trust Center

Support

Live working sessions available. We'll walk through your setup with you.

Contact support