75
Conditional

berkshirehathaway.com

Security posture assessment · Scanned February 15, 2026

Findings
4 · 3 · 1
Checks
8 passive

berkshirehathaway.com scored 75/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: HSTS Header. Positive signals: Known Breaches, TLS Configuration, CVE Exposure 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.

Ordered by priority · 4 items
1
Enable HSTS (HTTP Strict Transport Security)
Effort: < 1 hour   Owner: Web server administrator
high
The HSTS header is missing on berkshirehathaway.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance Impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
Remediation Steps
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://berkshirehathaway.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
2
Strengthen email authentication configuration
Effort: 2–4 hours   Owner: IT / DNS administrator
high
Email authentication is partially configured for berkshirehathaway.com but has gaps. Actions needed: configure DKIM. 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
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.berkshirehathaway.com
3
Enable DNSSEC on your domain
Effort: 1–3 days (depends on registrar)   Owner: DNS administrator / domain registrar
medium
Without DNSSEC, DNS responses for berkshirehathaway.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance Impact
NIST 800-53SC-20
Secure name/address resolution service
Remediation Steps
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec berkshirehathaway.com
4
Add optional security headers (Referrer-Policy, Permissions-Policy)
Effort: < 1 hour   Owner: Web server administrator
low
berkshirehathaway.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://berkshirehathaway.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
HSTS Header
Critical
Security Headers
Warning
DNS Configuration
Warning
DMARC / Email Security
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
CVE Exposure
Healthy
Certificate Hygiene
Healthy