72
stanford.edu
Findings
4
·
4
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
stanford.edu scored 72/100, meeting baseline requirements but with 4 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, DNS Configuration, Security Headers all passed.
4 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 · 4 items
1
Strengthen email authentication configuration
Email authentication is partially configured for stanford.edu 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.stanford.edu
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 4 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
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance Impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
Remediation Steps
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://stanford.edu | grep -i strict
3
Upgrade to TLS 1.3
stanford.edu negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
Remediation Steps
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect stanford.edu:443 -tls1_3
4
Review certificate configuration
Certificate issues found for stanford.edu: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
Scan Findings
DMARC / Email Security
Warning
TLS Configuration
Warning
HSTS Header
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
DNS Configuration
Healthy
Security Headers
Healthy
CVE Exposure
Healthy