Every Layer of
Application Security
From APK binary heuristics to repository SAST and dependency CVE scanning, Strata Security covers mobile binaries and source code repositories alike.
Looking for the product overview instead? See the Commercial Platform page.
Platform Capabilities
Static Analysis Engine
No runtime instrumentation. Strata Security analyses APK/IPA binaries and source repositories purely from static signals — manifests, bytecode, source files, and metadata.
VirusTotal Integration
When VirusTotal is configured, each mobile scan looks up the file's SHA-256 hash through the VirusTotal API. Detections appear as findings in your report.
Secret & Credential Detection
Regex-backed scanning surfaces hardcoded API keys, OAuth tokens, private keys, and connection strings across up to 5,000 files per repository, before they reach production.
Dependency CVE Scanning
Package manifests are parsed (npm, PyPI, Maven, Gradle) and every dependency is checked against the OSV database for known CVEs — with severity, fix version, and CVE IDs.
Team Workspaces
Invite your security team, organise scans into projects, and share findings across your organisation with role-based access control.
Results in <60 Seconds
Optimised pipeline processes most APKs and IPAs in under 30 seconds. Repository scans — including SAST and dependency lookups — typically complete in under 60 seconds.
Private & Secure
Files are streamed directly to the analysis engine. Content hashing prevents duplicate processing. Files and results are permanently deleted when your plan's retention period ends.
Unified Risk Scoring
Every assessment, mobile or repository, produces a risk score from 0 to 100 and a risk level (Low to High for mobile scans, Low to Critical for repository scans) based on weighted findings, dependency severity, and secret confidence.
APK Analysis — In Depth
Permission Intelligence
Strata Security checks every declared permission against a list of high-risk Android permissions. Each high-risk permission becomes a High severity finding mapped to OWASP Mobile Top 10 (2024) M6 (privacy) or M8 (misconfiguration), and dangerous permissions raise the overall risk score.
Special attention is paid to critical permissions like READ_CALL_LOG, SYSTEM_ALERT_WINDOW, and REQUEST_INSTALL_PACKAGES.
Manifest & DEX Analysis
Beyond permissions, Strata Security inspects the full AndroidManifest.xml for exported components, debug flags, backup settings, and cleartext traffic declarations.
DEX string scanning catches hardcoded API keys and other embedded secrets that manifest-only scanners miss, and the scan also flags plain http:// URLs and checks whether the code is obfuscated.
http://192.168.1.100/api/v1
google_api_key: [REDACTED]
IPA Analysis — In Depth
App Transport Security & Info.plist
iOS security largely lives in two places: Info.plist and the App Transport Security configuration. Strata Security reads both and reports ATS exceptions and unsafe settings.
NSAllowsArbitraryLoads is raised as a High severity finding under OWASP M5 (Insecure Communication), and per-domain exceptions are listed in the scan results.
NSAllowsArbitraryLoads: true // ⚠ M5
NSExceptionDomains: {
"api.example.com": {
NSExceptionAllowsInsecureHTTPLoads:
true // listed
}
}
}
Repository Scanning — In Depth
Secret & Sensitive File Detection
Strata Security walks up to 5,000 files in a cloned or uploaded repository (skipping dependency and build folders) looking for hardcoded secrets: API keys, OAuth tokens, private key material, database connection strings, and more, using a curated set of high-signal regex rules.
Sensitive file patterns (private keys, .env, credentials.json, SSH keys) are detected regardless of content and flagged before they can be exploited post-leak.
.env files, service account JSON, and keystore filesconfig/service-account.json
SAST & Code Vulnerability Analysis
Strata Security's static application security testing engine scans Python, JavaScript, TypeScript, Java, Kotlin, and Swift, flagging injection sinks, SSRF, unsafe deserialization, weak cryptography, and other exploitable patterns.
Each code finding is mapped to an OWASP Web Top 10 (2021) category (or, for AI findings, an OWASP LLM category) and a CWE identifier, giving developers the exact remediation context they need without leaving the report.
Dependency CVE Scanning
Strata Security parses every package manifest it finds — package.json, requirements.txt, pom.xml, Gradle build files, and lockfiles — then queries the OSV (Open Source Vulnerabilities) database for known CVEs in each pinned version.
Results include the CVE IDs, the advisory's severity, the version that fixes it when the advisory lists one, and links to the advisory, giving engineers the upgrade target without additional research.
AI & LLM Integration Analysis
As applications connect directly to AI providers, the integration boundary itself becomes a real attack surface. Strata Security detects 8 of the 10 OWASP Top 10 for LLM Applications categories — prompt injection, sensitive data sent unredacted to third-party AI APIs, unsafe model loading, and unsanitized AI output flowing into dangerous sinks.
Every finding maps to its OWASP LLM Top 10 category and a CWE identifier, while three categories (excessive agency, vector/embedding access control, unbounded consumption) rely on low-confidence heuristics that need human review.
Reports Clients Actually Read
Strata Security generates structured, professional-grade security reports — ready to send directly to development teams or executive stakeholders.
Executive Summary
Every PDF opens with a high-level risk overview — overall score, finding counts by severity, and the highest-priority issues. Designed for both developers and executive stakeholders.
Finding Evidence
Each finding includes the evidence that triggered it and its OWASP category; repository findings add the affected file and line and a CWE identifier for full traceability.
Remediation Guidance
Every finding ships with actionable fix instructions — tailored to the language and framework. No vague recommendations, just the specific change needed.
Multiple Export Formats
Export as a polished PDF for delivery (Pro and Team), structured JSON for CI/CD integration, or SARIF 2.1.0 for repository scans. Repository reports include OWASP Web Top 10 and CWE mapping sections.
Start Scanning for Free
1 scan per day, no credit card required. Upgrade when you need more.