Security Posture
A unified view of all security findings across your domains, cloud accounts, and repositories.
Security Posture
Your attack surface is everything that is exposed to potential attackers -- domains, subdomains, cloud resources, code repositories, and the services running on them. The larger your attack surface, the more opportunities exist for something to go wrong.
Seenty continuously scans your assets and consolidates all security findings into a single view, so you can prioritize and remediate issues before they are exploited.
What Seenty scans for
Seenty organizes findings into three categories:
- Misconfigurations -- Settings or configurations that weaken your security posture. Examples include missing email authentication records (SPF, DKIM, DMARC), public cloud storage buckets, overly permissive firewall rules, and dangling DNS records.
- Vulnerabilities -- Known software flaws (CVEs) in the technologies running on your domains or in the dependencies used by your repositories. Each vulnerability includes a CVSS score and remediation guidance.
- Secrets -- API keys, tokens, passwords, and private keys that have been accidentally committed to source code. Even a single exposed credential can lead to a full compromise.
Severity levels
Every finding is assigned a severity level based on its potential impact:
| Severity | Description |
|---|---|
| Critical | Immediate risk of exploitation. Requires urgent action -- for example, an exposed AWS root access key or a publicly writable S3 bucket. |
| High | Significant risk that should be addressed quickly. Examples include open SSH ports to the internet or IAM users without MFA. |
| Medium | Moderate risk that should be planned for remediation. Missing DMARC records or outdated SSL configurations fall here. |
| Low | Minor issues that represent best-practice improvements rather than active threats. |
| Info | Informational findings with no direct security impact, but useful for visibility -- such as detected technologies or DNS record details. |
Finding sources
Findings come from different scanning sources depending on the type of asset:
| Source | What it covers |
|---|---|
| Internal | Domain and subdomain scans -- DNS, SSL, technologies, headers, exposed services |
| AWS | IAM, S3, Security Groups, and other AWS resource configurations |
| Azure | RBAC, Storage, NSG, and other Azure resource configurations |
| Repository | Secrets in git history, vulnerable dependencies, IaC issues, Dockerfile problems |
The Security Posture dashboard
The Security Posture overview page gives you a high-level picture of your security health:
- Severity breakdown -- Stat cards showing counts by severity (Critical, High, Medium, Low) so you can spot where to focus first.
- Trend charts -- Track how your finding counts change over time. A downward trend means your team is remediating faster than new issues appear.
- Source distribution -- See which asset types are generating the most findings, helping you decide where to invest in hardening.
- Recent findings -- A live feed of the latest detections across all sources.
Explore by category
Misconfigurations
DNS, cloud, and infrastructure configuration issues that weaken your security posture.
Vulnerabilities
Known CVEs in your domain technologies and repository dependencies.
Secrets
Leaked credentials, API keys, and tokens found in your codebases.
Finding Lifecycle
Understand how findings move through Open, Acknowledged, Resolved, and False Positive states.