65
sbstransit.com.sg
Findings
2
·
6
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
sbstransit.com.sg scored 65/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, CVE Exposure all passed.
6 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 · 6 items
1
Strengthen email authentication configuration
Email authentication is partially configured for sbstransit.com.sg but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. 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
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.sbstransit.com.sg
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 6 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 sbstransit.com.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 sbstransit.com.sg
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://sbstransit.com.sg | grep -i strict
4
Upgrade to TLS 1.3
sbstransit.com.sg 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 sbstransit.com.sg:443 -tls1_3
5
Add optional security headers (Referrer-Policy, Permissions-Policy)
sbstransit.com.sg has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://sbstransit.com.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
6
Review certificate configuration
Certificate issues found for sbstransit.com.sg: 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
TLS Configuration
Warning
DMARC / Email Security
Warning
DNS Configuration
Warning
HSTS Header
Warning
Security Headers
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
CVE Exposure
Healthy