Google Drive Integration
Connect Google Workspace shared drives to Cremit Argus. Scan Docs, Sheets, Slides, and uploaded files for hardcoded API keys and credentials.
About this guide
This comprehensive guide will walk you through the complete setup process. Expected completion time: 5-10 minutes.
Overview
Argus's Google Drive integration scans Google Docs, Sheets, Slides, and uploaded files in shared drives for pasted credentials, API keys, and tokens. Uses OAuth, so no service account is required.
Prerequisites
- Google Workspace admin or shared drive Manager
- OAuth consent approval from a Workspace super admin (one-time)
- A Cremit Argus account
Step-by-Step Setup
Step 1: Open the Google Drive Scan Source in Argus
- In Argus, go to Configuration > Scan Sources and click New
- Select Google Drive as the source type
Step 2: Authorize Argus with OAuth
You will be redirected to Google's consent screen.
- Sign in with a Workspace account that has admin rights over the target drives
- Review the requested scopes: read-only access to Drive metadata and file content
- Click Allow to complete OAuth; you will be redirected back to Argus
Step 3: Choose drive scope
Decide which drives Argus should scan.
- Shared Drives: recommended for org-wide coverage; list is populated automatically
- My Drive: per-user drive (typically skipped for org scans)
- Specific folders: narrow the scan to a subtree if a full shared drive is too large
Step 4: Start the initial scan
Argus begins processing selected drives. Initial scan speed depends on total object count.
- Progress is visible in real time on the Scan Source detail page
- Subsequent scans are incremental and only process files changed since the last run
Verification
To confirm the integration is configured correctly:
- The OAuth connection shows Connected status
- Selected drives appear under Targets with recent Last Scan timestamps
- A sample of processed file paths appears in the Activity log
- No permission errors appear after the first scan completes
Troubleshooting
Issue: OAuth consent fails with 'This app is blocked.'
- Solution: A Workspace super admin must approve the Cremit Argus app in the Admin Console under Security > API controls > App access control.
Issue: Shared drives do not appear even after OAuth succeeds.
- Solution: The authenticated account needs at least Content Manager access to the shared drive. Ask a drive owner to invite the account or use a dedicated service-type Workspace account.
Key Benefits
- OAuth-based install, no service account key file to manage
- Covers Docs, Sheets, Slides, and uploaded files in one pass
- Respects existing sharing permissions; Argus sees only what the authorized account can see
- Incremental scanning keeps ongoing cost low