SECURE v2.0
Security Workflows Quick Start
Get operational with autonomous security scanning and threat hunting in minutes
2
Security Agents
500
Scans/Dev/Mo
100
Threat Hunts/Mo
5min
Time to First Scan
Your Security Agents
Security AI
Continuous vulnerability scanning and security assessment
- Container image scanning (CVEs)
- Dependency vulnerability analysis
- SAST code analysis (ULTRA tier)
- Compliance framework checks
ThreatHunter AI
Proactive threat detection and intelligence
- Threat hunting queries
- IOC detection and validation
- MITRE ATT&CK correlation
- Attack path analysis (ULTRA tier)
Quick Start in 3 Steps
1
Install & Configure
# Install CLI
npm install -g @autonoma-io/code
# Configure API key
autonoma config set api-key $AUTONOMA_API_KEY
# Initialize SECURE
autonoma secure init2
Run Your First Scan
CLI
# Scan container
autonoma secure scan container \
--image myapp:latest
# Scan dependencies
autonoma secure scan deps --path .API
curl -X POST \
'https://api.theautonoma.io/v1/secure/scan' \
-H 'Authorization: Bearer $KEY' \
-d '{"image": "myapp:latest"}'3
Start Threat Hunting
CLI
# Hunt for threats
autonoma secure hunt \
--query "failed logins > 10" \
--timeframe 24h
# Check IOC
autonoma secure ioc check \
--ip 192.168.1.100API
curl -X POST \
'https://api.theautonoma.io/v1/secure/hunt' \
-H 'Authorization: Bearer $KEY' \
-d '{"query": "failed logins"}'Common Workflows
PR Security Gate
Automatic security scanning on pull requests
autonoma secure integrate github \
--org your-org \
--block-on-criticalResult: PRs blocked if critical vulnerabilities found
CI/CD Container Scan
Scan container images in your build pipeline
autonoma secure scan container \
--image $ECR_IMAGE:$TAG \
--fail-on criticalResult: Build fails if critical CVEs detected
Threat Hunting Campaign
Scheduled threat hunting based on risk profile
autonoma secure hunt campaign \
--profile high-risk \
--schedule "0 */6 * * *"Result: Continuous threat detection every 6 hours
Attack Path Analysis
Map potential attack vectors (ULTRA tier)
autonoma secure analyze path \
--target production \
--include-mitreResult: Visual attack path with MITRE mapping
Time-to-Value Checklist
Day 1
- Install CLI and configure API key
- Initialize SECURE for your project
- Run first container scan
- Review baseline security posture
Day 2
- Connect GitHub for PR gates
- Enable Security Hub integration
- Configure Jira for tickets
- Start first threat hunting campaign
Week 1
- All repositories connected
- Automated scanning in CI/CD
- Threat hunting on schedule
- First compliance report generated
Ready to Secure Your SDLC?
Start with SECURE or upgrade to PLATFORM for full SDLC automation