80
broadcom.com
Findings
5
·
3
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
broadcom.com scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, Known Breaches, DMARC / Email Security all passed.
3 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 · 3 items
1
Upgrade to TLS 1.3
broadcom.com 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 broadcom.com:443 -tls1_3
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 3 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 (Referrer-Policy, Permissions-Policy)
broadcom.com has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://broadcom.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Certificate issues found for broadcom.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
Scan Findings
TLS Configuration
Warning
Security Headers
Warning
Certificate Hygiene
Warning
DNS Configuration
Healthy
Known Breaches
Healthy
DMARC / Email Security
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy