Getting Started with Drata: Complete SOC 2 Setup Guide
Drata provides customizable policy templates that satisfy SOC 2 requirements. Configuring policies involves reviewing templates, customizing them for your organization, and distributing them for employee acknowledgment. What we tell clients is that policy configuration is where many teams either rush and create audit risk, or overthink and lose momentum — the right approach is thorough but efficient.
Key Takeaways
- •Prioritize integrations in order of control coverage: cloud provider, identity provider, code repository, HR platform, endpoint management, monitoring, vulnerability scanning
- •Start employee training and policy acknowledgment workflows as soon as policies are approved — do not wait until the last minute
- •Use the Drata compliance dashboard to identify and remediate gaps before engaging your auditor, not after
This playbook is designed for compliance leads and engineering teams that have recently purchased Drata or are evaluating the platform during a trial. Every section follows the recommended setup order, with specific decisions explained and common configuration mistakes we see teams make flagged throughout. If you would rather not run this setup and ongoing monitoring yourself, our breakdown of Agency as a fully managed alternative to Drata covers when a done-for-you program makes more sense than the DIY route.
For the next operating decision, compare Drata pricing through Agency with who can manage Drata. Confirm the work included, the evidence you need, and who will own implementation before committing to a provider.
Which stages determine the implementation schedule?
In our experience, Drata's implementation is one of the fastest in the GRC platform category. The following timeline assumes a team of one compliance lead with part-time engineering support — which is how most of our clients start.
| Phase | Timeline | Key Activities |
|---|---|---|
| Workspace setup and framework selection | Day 1 | Create workspace, select SOC 2 framework, configure company profile |
| Cloud and identity integrations | Days 1-3 | Connect AWS/GCP/Azure, identity provider, HR platform |
| Agent deployment | Days 3-7 | Deploy Drata agent to all employee endpoints |
| Remaining integrations | Days 4-7 | Code repositories, endpoint management, monitoring, vulnerability scanning |
| Policy configuration | Days 5-10 | Customize and publish policy templates |
| Personnel onboarding | Days 7-10 | Invite employees, assign roles, trigger training and acknowledgments |
| Control review and gap remediation | Days 10-14 | Review control status, address failing controls, verify evidence flow |
Step 1: Workspace Setup and Framework Selection
Initial Configuration
When you first log into Drata, you will configure your workspace with foundational company information. We walk our clients through this step-by-step:
-
Company profile: Enter your company name, legal entity, industry, headcount, and primary location. This information populates your system description and determines which controls and integrations are most relevant.
-
Framework selection: Select SOC 2 as your primary framework. Drata supports 35+ frameworks — if you plan to pursue ISO 27001, HIPAA, or other frameworks alongside SOC 2, we recommend enabling them now so controls are cross-mapped from the start.
-
Trust Service Criteria selection: Choose which criteria to include in your SOC 2 scope. Security (Common Criteria) is mandatory. Add Availability, Processing Integrity, Confidentiality, or Privacy based on your customer requirements and business model.
-
Audit period: Set your intended audit observation period dates. For Type I, this is a point-in-time date. For Type II, this defines the start and end of your observation window. Setting this early helps Drata track evidence collection against your timeline.
Configuration Recommendations
- Start with Security only unless customers have specifically requested additional criteria. In our experience, cross-framework mapping is significantly more efficient when enabled from the start rather than retrofitted later.
- Set realistic audit dates — if you have not yet engaged an auditor, estimate conservatively and adjust later. We see teams create unnecessary stress by setting aggressive dates before their program is actually ready.
Step 2: Connect Cloud Infrastructure Integrations
Cloud provider integrations are the highest-priority connections because they provide evidence for the largest number of SOC 2 controls. We always advise clients to start here.
AWS Integration
Drata's AWS integration uses a CloudFormation stack or IAM role to scan your AWS environment:
- Navigate to the Integrations page and select AWS
- Choose your connection method (we recommend CloudFormation for simplicity)
- Deploy the CloudFormation template in your AWS account — this creates a read-only IAM role that grants Drata permission to scan your configuration
- Verify the connection and run the initial scan
The AWS integration monitors security groups, S3 bucket policies, encryption settings, IAM configurations, CloudTrail logging status, and other security-relevant settings across your AWS services.
GCP Integration
For Google Cloud Platform:
- Create a service account with the required read-only roles
- Enable the APIs that Drata needs to scan your environment
- Provide the service account credentials to Drata
- Run the initial scan to verify connectivity
Azure Integration
For Microsoft Azure:
- Register an application in Microsoft Entra ID
- Assign the Reader role at the subscription level
- Provide the application credentials to Drata
- Verify the connection and initial scan results
Post-Connection Verification
After connecting your cloud provider, review the initial scan results on your Drata dashboard. You will likely see several failing controls related to cloud configuration — unencrypted storage buckets, overly permissive security groups, or disabled logging. We tell clients not to panic at this stage. These are expected findings that you will remediate during the gap resolution phase, and they are exactly why you connected the integration early.
Step 3: Connect Identity Provider
Your identity provider integration is critical because it provides evidence for access management controls — user provisioning, MFA enforcement, and role-based access. In our experience, this is where many teams underestimate the cleanup work involved.
Supported Identity Providers
Drata integrates with major identity providers including:
- Google Workspace: Syncs user accounts, MFA status, admin roles, and device management
- Okta: Pulls user directory, MFA enrollment, application assignments, and group memberships
- Microsoft Entra ID (Azure AD): Syncs users, MFA configuration, conditional access policies, and group assignments
- JumpCloud: User directory, MFA status, and device management
- OneLogin: User provisioning, MFA configuration, and application assignments
Configuration Steps
- Navigate to Integrations and select your identity provider
- Authenticate with admin credentials and grant Drata the required read permissions
- Verify the user roster imports correctly — every employee should appear in Drata's personnel list
- Confirm MFA enforcement status is accurately reflected for all users
Common Issues
- MFA showing as non-compliant: If employees use hardware security keys or authenticator apps not directly visible to your identity provider, you may need to configure Drata to recognize alternative MFA methods. We see this frequently with teams using YubiKeys.
- Service accounts appearing as users: Exclude service accounts from the personnel roster if they are not human users. Drata allows you to categorize accounts appropriately — and we recommend doing this cleanup immediately rather than letting it linger.
- Contractor status: Mark contractors appropriately in Drata so they follow the correct compliance requirements. We advise establishing a clear contractor classification policy before onboarding begins.
Step 4: Deploy the Drata Agent
The Drata agent runs on employee endpoints (laptops and desktops) to verify device compliance — disk encryption, screen lock, firewall, OS updates, and antivirus status. In our experience, agent deployment is the step most likely to stall if not managed proactively.
Deployment Strategy
| Approach | Best For | Effort |
|---|---|---|
| MDM-managed deployment | Organizations with Jamf, Kandji, Intune, or similar MDM | Low — push via MDM silently |
| Self-service installation | Small teams without MDM | Moderate — employees install individually |
| Hybrid | MDM for managed devices, self-service for BYOD | Moderate — covers both scenarios |
Deployment Steps
- Download the Drata agent package for macOS, Windows, and Linux from the Drata dashboard
- Distribute via your MDM tool or send installation instructions to employees
- Employees install the agent and authenticate with their company email
- The agent begins reporting device compliance status to Drata within minutes
Endpoint Compliance Requirements
The Drata agent checks for the following baseline requirements:
- Disk encryption enabled (FileVault on macOS, BitLocker on Windows)
- Screen lock configured (we recommend a five-minute timeout)
- Firewall enabled
- OS version current (within supported update window)
- Antivirus/endpoint protection running (if applicable to your security policy)
Every employee device that accesses company systems must have the Drata agent installed. Track deployment progress on the Drata personnel dashboard, which shows which employees have installed the agent and which devices are compliant.
Step 5: Connect Remaining Integrations
After cloud, identity, and endpoint integrations are established, connect the remaining tools in your stack. We recommend tackling these in priority order based on control coverage.
Code Repository Integration
Connect GitHub, GitLab, or Bitbucket to provide evidence for change management controls:
- Branch protection rules on production branches
- Code review requirements (pull request approvals)
- Deployment documentation and change records
Verify that your main production branches require at least one approving review before merge and that direct commits to production branches are blocked. We cannot stress this enough — this is one of the most common audit findings we see.
HR Platform Integration
Connect BambooHR, Gusto, Rippling, or your HR system to synchronize:
- Employee roster with hire dates and termination dates
- Department and role assignments
- Onboarding and offboarding event tracking
Monitoring and Vulnerability Scanning
Connect your monitoring and security scanning tools:
- Monitoring: Datadog, PagerDuty, or other alerting tools for system operations evidence
- Vulnerability scanning: Snyk, Qualys, Crowdstrike, or other scanning tools for vulnerability management evidence
Integration Prioritization
If your team's bandwidth is limited, we recommend prioritizing integrations in this order:
- Cloud provider (highest control coverage)
- Identity provider (access management controls)
- Code repository (change management controls)
- HR platform (personnel security controls)
- Endpoint management/MDM (endpoint compliance evidence)
- Monitoring tools (system operations controls)
- Vulnerability scanning (vulnerability management controls)
Step 6: Configure Policies
Required Policies
| Policy | Purpose | Customization Level |
|---|---|---|
| Information Security Policy | Overarching security governance | Moderate — update roles, responsibilities, and organizational structure |
| Access Control Policy | User provisioning and access management | Moderate — align with your identity provider and access review cadence |
| Change Management Policy | Infrastructure and application change control | High — must reflect your actual deployment process |
| Incident Response Plan | Security incident detection and response | Moderate — customize escalation contacts and communication channels |
| Risk Assessment Policy | Risk identification and management methodology | Low — template is generally sufficient |
| Data Classification Policy | Data handling categories and requirements | Moderate — define your specific data categories |
| Acceptable Use Policy | Employee guidelines for system usage | Low — template is generally sufficient |
| Vendor Management Policy | Third-party security assessment | Moderate — align with your vendor review cadence |
| Business Continuity and Disaster Recovery Plan | Recovery procedures and testing | High — must reflect your actual infrastructure and recovery capabilities |
| Human Resources Security Policy | Background checks, training, offboarding | Moderate — align with your HR processes |
Policy Configuration Process
- Review each template in the Drata policy library
- Customize sections that reference your specific organizational structure, tools, and processes
- Route policies to management (CTO, CEO, or security lead) for formal approval
- Publish policies and trigger employee acknowledgment workflows
- Track acknowledgment completion in Drata's personnel dashboard
Common Mistakes
- Not customizing templates: We see this constantly — teams use templates verbatim without adapting them to their organization, and it creates real audit risk. Your auditor will verify that policies reflect actual practices.
- Skipping management approval: Policies must have documented approval from management before distribution. We recommend getting this sign-off in writing, not just verbally.
- Delaying acknowledgment tracking: Start employee policy acknowledgment workflows as soon as policies are approved. In our experience, this is the step most likely to cause last-minute compliance gaps because employees procrastinate on reading and signing policies.
Step 7: Personnel Onboarding and Training
Inviting Employees
- Import your employee roster from the connected HR platform (or manually if no HR integration)
- Assign compliance roles — identify who is responsible for security, compliance, engineering, and HR functions
- Send Drata invitations to all employees who need to complete compliance tasks
Security Awareness Training
Drata integrates with security training providers and offers built-in training modules. We recommend setting aggressive but realistic deadlines:
- Assign security awareness training to all employees
- Track completion progress on the personnel dashboard
Background Checks
Verify that background checks are on file for all employees:
- Connect your background check provider if Drata supports integration
- Upload background check documentation for employees screened through other providers
- Document any exceptions for existing employees who were not screened and establish a plan for future hires — we always recommend documenting a clear exception rationale and forward-looking policy rather than trying to retroactively screen your entire team
Step 8: Control Review and Gap Remediation
After all integrations are connected and policies are in place, conduct a comprehensive review of your Drata compliance dashboard. This is the stage where we spend the most hands-on time with clients, because gap remediation is where real security improvements happen.
Dashboard Review
Drata organizes controls by Trust Service Criteria category. We recommend reviewing each category and identifying:
- Passing controls: Evidence is flowing automatically and meeting requirements
- Failing controls: Configuration issues, missing evidence, or non-compliant settings
- Needs attention: Manual evidence required or pending human action
Common Gaps and Remediation
| Common Gap | Remediation Action | Typical Effort |
|---|---|---|
| MFA not enforced for all users | Enable MFA requirement in identity provider | Depends on scope and readiness |
| Cloud storage not encrypted | Enable default encryption on S3 buckets/Cloud Storage/Blob Storage | Depends on scope and readiness |
| No audit logging configured | Enable CloudTrail/Cloud Audit Logs/Azure Activity Logs | Depends on scope and readiness |
| Branch protection not enabled | Configure branch protection rules on production repositories | 30 minutes |
| Missing vulnerability scanning | Deploy and configure a vulnerability scanner | Depends on scope and readiness |
| Incomplete employee training | Send reminders and escalate to managers | Depends on scope and readiness |
| No formal risk assessment | Conduct risk assessment using Drata's risk module | Depends on scope and readiness |
Audit Readiness Checklist
Before engaging your auditor, we recommend verifying the following in Drata:
AICPA & CIMA’s SOC overview describes CPA assurance services. It defines the assurance context; it does not establish vendor rankings, market prices, or a particular company’s readiness.
Frequently Asked Questions
How long does it take to set up Drata for SOC 2?
Which Drata integrations should I connect first?
What does the Drata agent check on employee laptops?
Why does Drata show failing controls right after I connect my cloud account?
Do I need to customize Drata's policy templates?

Tyler Carbone
Managing Director and Cofounder
Tyler Carbone is a Managing Director and Cofounder of Agency and one of the industry's leading voices on governance, risk, and compliance. He holds degrees from Harvard and a JD/MBA from the University of Virginia, and previously worked in cybersecurity at Deloitte. Tyler has helped hundreds of companies operate SOC 2, ISO 27001, HIPAA, and GDPR programs.
LinkedIn