72
mediacorp.sg
Findings
5
·
1
·
2
Checks
8 passive
Executive Summary
AI-GENERATED
mediacorp.sg scored 72/100, meeting baseline requirements but with 1 finding that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security, Security Headers. Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.
3 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 · 3 items
1
Set up email authentication (DKIM)
Without email authentication, anyone can send emails that appear to come from mediacorp.sg. This is the most common vector for phishing attacks targeting employees and customers. DKIM is 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@mediacorp.sg
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 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
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on mediacorp.sg: CSP, 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 Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://mediacorp.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for mediacorp.sg 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 .sg TLD
4
Verify: dig +dnssec mediacorp.sg
Scan Findings
DMARC / Email Security
Critical
Security Headers
Critical
DNS Configuration
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy
Certificate Hygiene
Healthy