75
newrelic.com
Findings
5
·
2
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
newrelic.com scored 75/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: HSTS Header, Known Breaches, DNS Configuration all passed.
3 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 · 3 items
1
Add missing security headers (X-Frame-Options, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on newrelic.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://newrelic.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 3 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
Upgrade to TLS 1.3
newrelic.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 newrelic.com:443 -tls1_3
3
Review certificate configuration
Certificate issues found for newrelic.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
Scan Findings
Security Headers
Critical
TLS Configuration
Warning
Certificate Hygiene
Warning
HSTS Header
Healthy
Known Breaches
Healthy
DNS Configuration
Healthy
DMARC / Email Security
Healthy
CVE Exposure
Healthy