68
firebase.google.com
Findings
4
·
2
·
2
Checks
8 passive
Executive Summary
AI-GENERATED
firebase.google.com scored 68/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security, Security Headers. Positive signals: TLS Configuration, 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
Set up email authentication (DMARC, SPF, DKIM)
Without email authentication, anyone can send emails that appear to come from firebase.google.com. This is the most common vector for phishing attacks targeting employees and customers. DMARC, 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
Remediation Steps
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:dmarc-reports@firebase.google.com
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
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
Add missing security headers (X-Frame-Options, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on firebase.google.com: X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance Impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
Remediation Steps
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://firebase.google.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for firebase.google.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 firebase.google.com
4
Review certificate configuration
Certificate issues found for firebase.google.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
Critical
Security Headers
Critical
DNS Configuration
Warning
Certificate Hygiene
Warning
TLS Configuration
Healthy
Known Breaches
Healthy
CVE Exposure
Healthy
HSTS Header
Healthy