68
drive.google.com
Findings
4
·
3
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
drive.google.com 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, Security Headers 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 drive.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@drive.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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for drive.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 drive.google.com
3
Upgrade to TLS 1.3
drive.google.com 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.
Remediation Steps
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect drive.google.com:443 -tls1_3
4
Review certificate configuration
Certificate issues found for drive.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
TLS Configuration
Warning
DNS Configuration
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
HSTS Header
Healthy
Security Headers
Healthy
CVE Exposure
Healthy