45
lacework.com
Findings
2
·
3
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
lacework.com scored 45/100 and does not meet the minimum security posture threshold. The most critical issue is: Upgrade TLS — deprecated protocol in use. This must be addressed before the vendor can be approved for procurement or data processing activities.
Critical gaps in: TLS Configuration. Positive signals: Known Breaches, 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.
Action Items
Ordered by priority · 4 items
1
Upgrade TLS — deprecated protocol in use
lacework.com is using unknown, which is deprecated and has known vulnerabilities. This is a compliance failure under PCI-DSS, HIPAA, and NIST guidelines. Immediate upgrade to TLS 1.2 minimum (TLS 1.3 preferred) is required.
Compliance Impact
PCI-DSS 4.0Req 4.2.1
Strong cryptography for transmission
NIST 800-52r2§3.4
TLS 1.0/1.1 must not be used
HIPAA§164.312(e)
Transmission security
Remediation Steps
1
Disable TLS 1.0 and 1.1 in your web server configuration
2
Enable TLS 1.2 and 1.3: ssl_protocols TLSv1.2 TLSv1.3
3
Remove weak ciphers: ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:...'
4
Verify: openssl s_client -connect lacework.com:443 -tls1_2
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
Strengthen email authentication configuration
Email authentication is partially configured for lacework.com 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.lacework.com
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for lacework.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 lacework.com
4
Review certificate configuration
Certificate issues found for lacework.com: . These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Consolidate certificate issuance to 1–2 trusted CAs
Scan Findings
TLS Configuration
Critical
DMARC / Email Security
Warning
DNS Configuration
Warning
Certificate Hygiene
Warning
HSTS Header
Error
Security Headers
Error
Known Breaches
Healthy
CVE Exposure
Healthy