75
lyft.com
Findings
3
·
5
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
lyft.com scored 75/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
5 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 · 5 items
1
Strengthen email authentication configuration
Email authentication is partially configured for lyft.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.lyft.com
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 5 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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for lyft.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 lyft.com
3
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://lyft.com | grep -i strict
4
Add optional security headers (CSP, Permissions-Policy)
lyft.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://lyft.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
5
Review certificate configuration
Certificate issues found for lyft.com: 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
DNS Configuration
Warning
HSTS Header
Warning
Security Headers
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
CVE Exposure
Healthy