Skip to main content
Cloud Run SAST & AI Remediation Engine

Automated SAST &
Code Security Scanner (OWASP:2021)

Enterprise-grade static application security testing powered by Semgrep AST taint-tracking and Google GenAI contextual validation. Detect OWASP Top 10:2021 security flaws, eliminate false positives, and generate instant code remediation patches.

100% Private (Zero Code Retention)
OWASP Top 10:2021 Standard
Automated AI Fix Patches
Executive & Technical VAPT PDF
Drag & Drop Your Project ZIP Archive Here
Supports PHP (Laravel, CodeIgniter, WordPress), JavaScript/TypeScript, Python, Java, Go, and Ruby (Up to 50MB)
Initializing Ephemeral Scanning Sandbox...
0%
[INIT] Connecting to AutoSAST Cloud Run Engine...

Vulnerability Assessment Report

ID: - 0s Target: Source Repository
0
Total Findings
0
Analyzed Code Files
0
Total Project Files
Medium
Overall Risk Level
Executive Summary & AI Remediation Priorities
Loading contextual security evaluation...
Severity Distribution
OWASP Top 10:2021 Categories

Comprehensive Findings Overview

# File & Line Severity OWASP Category Source Status Risk Impact Action

AutoSAST Security Architecture & Technical Authority Guide

Learn how the powerful synthesis of Abstract Syntax Tree (AST) pattern matching and Google GenAI contextual validation eliminates legacy false alarms and accelerates code remediation.

Why Semgrep AST Beats Legacy Regex Linters

Semgrep is an enterprise Static Application Security Testing (SAST) engine that parses source code into an Abstract Syntax Tree (AST) representation. Unlike legacy regex linters that trigger up to 80% false alarms on code comments, variable names, or harmless documentation strings, Semgrep understands program semantics and syntax hierarchy.

  • Source-to-Sink Taint Tracking: Traces tainted user inputs from controllers through services down to critical sinks (database queries, shell executions, HTML responses).
  • Blazing Fast Execution: Evaluates thousands of lines of source code in seconds without requiring compilation or build steps (*no build artifact dependencies*).
  • Broad Language Coverage: Native AST parsers for PHP, JavaScript, TypeScript, Python, Java, Go, Ruby, and C#.

The Role of Google GenAI in AutoSAST

While Semgrep provides fast raw syntax matches, it lacks broader architectural awareness. AutoSAST deploys Google GenAI (Gemini) as an Autonomous Tier-1 Security Reviewer to perform intelligent contextual verification.

  • False Positive Elimination: Intelligently analyzes whether framework protections (e.g. Laravel CSRF middleware or CodeIgniter prepared statements) protect the code path upstream.
  • Idiomatic Fix Patch Synthesis: Automatically drafts production-ready code patches (*fixed code*) following modern coding standards (e.g. prepared queries, password_hash with bcrypt).
  • Structured Audit POCs: Formulates concrete Proof of Concept (POC) verification steps with Burp Suite instructions for auditor validation.

The 5-Stage End-to-End Scanning Pipeline

How source code flows through AutoSAST from initial ingestion to certified PDF generation

01

Secure Ingestion

ZIP archives or Git repositories cloned with depth=1 are unpacked into an ephemeral memory sandbox.

02

AST Taint Mapping

Semgrep scans all discovered source files against curated OWASP Top 10:2021 and framework-specific rule packs.

03

GenAI Verification

Gemini AI verifies taint paths, filters false alarms, calculates CVSS likelihood/impact, and assigns confidence scores.

04

Remediation Synthesis

AI generates idiomatic code fix patches alongside detailed Proof of Concept (POC) verification instructions.

05

Zero-Retention Purge

All source code is completely purged from disk and memory. The final VAPT report is rendered for download.

OWASP Top 10:2021 Complete Reference Matrix

The globally recognized standard for web application security risks evaluated by AutoSAST:

Category Code Risk Profile & Characteristics Common Vulnerability Vectors & Mitigation Strategy
A01:2021
Broken Access Control
Users acting outside of intended permissions (IDOR, privilege escalation, unprotected administrative routes). Enforce deny-by-default access policies. Validate resource ownership server-side on every request using robust Role-Based Access Control (RBAC).
A02:2021
Cryptographic Failures
Sensitive data exposure through weak or outdated hashing (MD5, SHA1), hardcoded encryption keys, or unencrypted HTTP transit. Adopt modern password hashing algorithms (Argon2id, Bcrypt). Encrypt data-at-rest using AES-256-GCM and enforce TLS 1.3 with HSTS headers.
A03:2021
Injection
Hostile user input interpreted as commands (SQL Injection, Cross-Site Scripting / XSS, OS Command Injection via system/exec). Always utilize parameterized queries (Prepared Statements), context-aware output encoding (htmlspecialchars/Blade), and avoid raw shell execution functions.
A04:2021
Insecure Design
Fundamental architectural flaws created before code was written (lack of rate limiting, unauthenticated password reset endpoints). Incorporate Threat Modeling early in design phases. Enforce rate limiting across authentication endpoints and establish secure-by-default component patterns.
A05:2021
Security Misconfiguration
Default credentials left active, debug modes exposed in production (APP_DEBUG=true), or missing HTTP security headers. Disable verbose debug modes in production environments, enforce strict Content-Security-Policy (CSP) headers, and audit cloud infrastructure settings.
A06:2021
Vulnerable Components
Third-party packages (npm, Composer, Pip) running known CVE vulnerabilities or unmaintained dependencies. Regularly audit external libraries using composer audit or npm audit. Maintain active automated dependency update pipelines.
A07:2021
Identification & Auth
Weak credential policies, missing brute-force protection, credential stuffing vulnerabilities, or session fixation flaws. Implement Multi-Factor Authentication (MFA), require passwords of at least 8 characters (NIST SP 800-63B), and regenerate session IDs post-login.
A08:2021
Software Integrity
Applications executing untrusted code updates or deserializing hostile object streams without cryptographic validation. Avoid native language object deserialization with untrusted input; prefer strict JSON serialization. Digitally sign and verify auto-updates.
A09:2021
Security Logging Failures
Insufficient audit trails for authentication events, privilege escalation, or security exceptions, hindering breach detection. Record security-relevant events with precise UTC timestamps. Ensure logs never capture raw passwords or PII, and forward to SIEM monitors.
A10:2021
SSRF
Web server manipulated into making requests to internal or arbitrary endpoints (Server-Side Request Forgery). Sanitize and strictly whitelist destination domains and protocols. Block access to cloud instance metadata services (169.254.169.254) and RFC 1918 subnets.

Engineering Honesty: Inherent Boundaries of Static Analysis (SAST)

As security practitioners, it is critical to acknowledge that SAST (Static Application Security Testing) is not a silver bullet. SAST inspects code at rest without executing the runtime environment, giving it distinct strengths alongside clear boundaries:

  • Zero Runtime Environment Visibility: SAST cannot verify whether your production web server enforces Web Application Firewall (WAF) rules, Cloudflare rate limiting, or reverse proxy mitigations.
  • Complex Business Logic Flaws: Flaws such as price tampering, race conditions, or unauthorized coupon stacking typically require Dynamic Application Security Testing (DAST) or human penetration testing.
  • Best Practice Recommendation: Use AutoSAST as your essential first line of defense (Shift-Left Security) in development, and complement it with periodic manual penetration tests for comprehensive defense-in-depth.

Frequently Asked Questions (FAQ)

Never. AutoSAST strictly adheres to an ephemeral Zero Code Retention policy. ZIP archives or Git clones are unpacked into temporary containers on Google Cloud Run, analyzed directly in AST memory, and completely erased (shutil rmtree) immediately once report generation completes. No code is stored in databases.
For free public usage, ZIP archives can be up to 50MB with a recommended ceiling of 500 source code files per scan. Bulky dependency directories such as node_modules/, vendor/, and .git/ are automatically excluded to preserve speed and avoid scanning third-party vendor code.
AutoSAST supports semantic AST analysis for PHP (including Laravel, CodeIgniter, and WordPress), JavaScript, TypeScript, Python, Java, Go, Ruby, and C#. Rulesets are dynamically matched based on the file extensions discovered within your project tree.
OWASP Top 10:2021 is the current official, universally accepted global benchmark established by the OWASP Foundation. Subsequent revisions have not been officially published. This standard represents modern threat vectors, including Broken Access Control as the #1 critical risk.
As soon as the scan finishes, the green "Download PDF Report" button appears at the top right of the dashboard. Clicking this generates an executive-ready, professional VAPT PDF containing all findings, risk distribution metrics, and technical remediation notes suitable for leadership or compliance audits.

Free tool by NRTechStudio