VigilantAI
External Exposure Report
Generated: Apr 25, 2026
Target: example.com
example.com · April 2026
Your external security posture has been assessed
Risk Level
MediumExposure Score
60/100
80%
AI Confidence
14
Services exposed
3
Issues identified
What this means
This does not confirm compromise. It indicates how likely an attacker could gain access based on what is exposed — and what they could use to get there.
Likelihood of compromise
MEDIUM
Based on:
- • Exposed internet-facing services
- • Identity breach signals detected
An attacker could realistically attempt access using known credentials and exposed services.
Identity breach exposure
HIGH RISKCommon email patterns found in known breach datasets
Exposed patterns include common business email formats — admin@, support@, info@. These are frequently targeted in credential-reuse attacks.
Business impact
- •Moderate risk of unauthorized access if left unaddressed
- •Some services are visible to external automated scanners
- •Improvements recommended before next audit or insurance renewal
Likely attack path
1.Attacker obtains breached credentials from public datasets
2.Identifies exposed internet-facing service (e.g. web, DNS)
3.Attempts access using credential reuse or brute force
4.Gains foothold if authentication controls are weak
This is the most common real-world compromise path when identity exposure is detected.
Top risks contributing to access
HIGHSNMP (port 161) is exposed
Why it matters
This can reveal internal device information and configuration to anyone on the internet.
What to do
Block SNMP access from the public internet. Allow only trusted internal networks.
MEDIUMDNS (port 53) is exposed
Why it matters
Misconfigured DNS can be abused for amplification attacks or data exposure.
What to do
Restrict access or harden configuration if intentionally public.
MEDIUMPublic web services detected (ports 80, 443, 8080, 8443)
Why it matters
These are common entry points. Security depends on patching and proper configuration.
What to do
Enforce HTTPS, update software, and restrict unnecessary ports.
What to fix first
1Restrict DNS access (port 53)~10 minutes
2Redirect HTTP to HTTPS (port 80)~5 minutes
3Re-scan to confirm improvement~1 minute
Verification — what changed
Risk improved by 30 points
Remediation is working. Continue monitoring for new changes.
Before
60
Score before fixes
After
30
Score after fixes
Result
−30
Risk reduction
Want to reduce this risk?
Apply the fixes above and run a follow-up scan to verify improvement.
Generated by VigilantAI · getvigilantai.com
This report is a point-in-time external snapshot. It does not include internal systems or authenticated testing.