Solutions
Cloud and SaaS posture in the same risk model
A public storage bucket and an unpatched server should be prioritized on the same scale. Guardian normalizes both into one findings model with one remediation workflow.
Connectors
AWS
Cross-account IAM role preferred over long-lived keys.
- IAM, EC2, S3, VPC and security groups
- RDS and encryption posture
- CloudTrail, Config and GuardDuty
- Inspector and Security Hub findings
Azure
- Azure Resource Manager
- Entra identity risks
- Defender for Cloud recommendations
- Storage, Key Vault and App Services
- Network security groups
Google Cloud
- Projects and IAM
- Compute Engine
- Cloud Storage
- Firewall rules
- Cloud SQL
- Security Command Center
Microsoft 365 / Entra ID
- MFA and privileged roles
- Conditional Access
- Risky users and sign-ins
- Guest and dormant accounts
- SharePoint, OneDrive and Teams sharing
- Secure Score
Salesforce
- Administrators and dormant accounts
- Login and session security
- Profiles and permission sets
- MFA configuration
- OAuth applications
Email security
- SPF, DKIM and DMARC checks
- Defender for Office 365
- Proofpoint and Mimecast where configured
- Phishing and impersonation telemetry
No connection, no fake data
Until you authorize a connector, Guardian shows an onboarding state — never invented cloud findings. Each integration reports its real state: connected, permission required, authentication expired, sync running, sync failed, and last successful sync.