88
wiz.io
Findings
6
·
2
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
wiz.io scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, HSTS Header, CVE Exposure all passed.
2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
Action Items
Ordered by priority · 2 items
1
Strengthen email authentication configuration
Email authentication is partially configured for wiz.io but has gaps. Actions needed: add SPF record. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
Remediation Steps
1
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Verify with: nslookup -type=txt _dmarc.wiz.io
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 2 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Add optional security headers (X-Frame-Options, Permissions-Policy)
wiz.io has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://wiz.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
Scan Findings
DMARC / Email Security
Warning
Security Headers
Warning
TLS Configuration
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy
Known Breaches
Healthy
DNS Configuration
Healthy
Certificate Hygiene
Healthy