Getting started
Launch AiVRIC quickly with a secure baseline. Follow the step-by-step flow and mirror how GitLab documents clear ownership and actions.
1) Plan workspaces
Map environments to workspaces (e.g., prod, staging, R&D). Align each with data sensitivity and owners.
- Define owners in IAM groups.
- Enable SSO and SCIM before inviting users.
2) Secure access
Use SSO + MFA; grant least-privilege roles in cloud accounts. Configure break-glass with short-lived tokens.
- Map roles to AiVRIC groups.
- Audit login attempts weekly.
3) Connect systems
Connect cloud accounts, Kubernetes, GitHub, and ticketing to start control monitoring.
- Use deployment templates per connector.
- Verify data collection scope.
4) Apply guardrails
Enable policy packs for compliance (SOC 2, ISO 27001) and AI safeguards (PII, secrets, jailbreaks).
- Run dry-runs first; review impact.
- Promote to enforce mode after sign-off.
Connect your environment
All connectors are powered by CloudSignals+RiskOps™ — AiVRIC's continuous posture monitoring and compliance automation engine. Each connected provider is audited every 24 hours automatically.
| Integration | Purpose | Quick action |
|---|---|---|
| AWS | Continuously monitor IAM hygiene, network rules, and resource configurations for drift. | Deploy read-only IAM role via CloudFormation Quick Link; launch scan. |
| Microsoft Azure | Audit subscriptions for misconfigurations, identity posture, and policy compliance. | Create App Registration + Service Principal; enter Tenant ID, Client ID, and Secret. |
| Google Cloud Platform | Scan GCP projects for posture drift and framework control gaps. | Create read-only Service Account; paste JSON key into AiVRIC. |
| Kubernetes | Secure cluster workloads, service account access, and runtime configurations. | Paste kubeconfig; apply read-only RBAC resources for managed clusters. |
| GitHub | Protect repos, branch protections, secrets exposure, and pipeline tokens. | Connect via PAT, OAuth App, or GitHub App with least-privilege scopes. |
| Microsoft 365 | Monitor tenant controls for SOC 2, PCI DSS, and CMMC compliance. | Register Entra ID app; configure certificate authentication for full check coverage. |
| MongoDB Atlas | Audit database cluster configurations and access controls. | Generate an Atlas API key pair; paste Public and Private keys into AiVRIC. |
| Alibaba Cloud | Monitor resource configurations and IAM posture for drift. | Use RAM Role Assumption (recommended) or static credentials for quick scans. |
| Ticketing (Jira / ServiceNow) | Send findings to owners and track remediation status bidirectionally. | Connect via OAuth; map severity levels to ticket priority in Settings. |
Collaborate and ship
- Approvals: Require dual approval for high-impact guardrails; log who approved.
- 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: Use staging workspaces to validate connectors before production.
- Ownership: Keep owners visible in tickets and in the left rail for fast navigation.
Resources
Connector setup guides
Step-by-step instructions for AWS, Azure, GCP, Kubernetes, GitHub, M365, MongoDB Atlas, and Alibaba Cloud.
View all connectorsCloudSignals+RiskOps overview
Understand the posture monitoring engine: scan cadence, compliance mapping, alerts, SIEM integration, and reporting.
Read the overviewTrust Center
Access SOC 2, penetration testing summaries, and data handling details.
Open Trust Center