Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
kaiserpermanente.org scored 68/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security. Positive signals: Known Breaches, HSTS Header, CVE Exposure all passed.
4 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How kaiserpermanente.org compares
Grade distribution across 2519 companies we've scanned. kaiserpermanente.org scores better than 37% of them.
79
A+
25
A
184
A-
190
B+
73
B
351
B-
121
C+
113
C
324
C-
117
D+
93
D
236
D-
613
F
kaiserpermanente.org — Grade D+ (68/100)
2519 companies scanned
Security checks
Each check inspects a different part of kaiserpermanente.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Issues: DMARC policy is 'none' (monitoring only, no enforcement); No SPF record found; No DKIM records found for common selectors (may use non-standard selectors).
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
DNS Configuration
Strengths: 3 nameservers configured (ea-dns25.kp.org., ea-dns36.kp.org., ea-dns14.kp.org.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 372 days remaining; Issued by Sectigo Limited.
Recommended actions
4 items
Steps to improve kaiserpermanente.org's security grade, ranked by impact.
1
Set up email authentication (SPF, DKIM)
Without email authentication, anyone can send emails that appear to come from kaiserpermanente.org. This is the most common vector for phishing attacks targeting employees and customers. SPF, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for kaiserpermanente.org 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
How to fix this
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 .org TLD
4
Verify: dig +dnssec kaiserpermanente.org
3
Upgrade to TLS 1.3
kaiserpermanente.org 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.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect kaiserpermanente.org:443 -tls1_3
4
Add optional security headers (Referrer-Policy, Permissions-Policy)
kaiserpermanente.org has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://kaiserpermanente.org | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=none
Issues: DMARC policy is 'none' (monitoring only, no enforcement); No SPF record found; No DKIM records found for common selectors (may use non-standard selectors).
SPF Record
Missing
No SPF record found.
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 372 days remaining; Issued by Sectigo Limited.
DNSSEC
Not enabled
Strengths: 3 nameservers configured (ea-dns25.kp.org., ea-dns36.kp.org., ea-dns14.kp.org.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.