70
Conditional

tpg.com.sg

Security posture assessment · Scanned February 15, 2026

Findings
4 · 3 · 1
Checks
8 passive

tpg.com.sg scored 70/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: Security Headers. Positive signals: TLS Configuration, DNS Configuration, Known Breaches all passed.

4 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.

Ordered by priority · 4 items
1
Strengthen email authentication configuration
Effort: 2–4 hours   Owner: IT / DNS administrator
high
Email authentication is partially configured for tpg.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.tpg.com.sg
2
Add missing security headers (CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy)
Effort: 1–2 hours   Owner: Web server administrator
high
4 of 5 recommended security headers are missing on tpg.com.sg: CSP, 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 Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://tpg.com.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review potential CVE exposure in detected software
Effort: 2–4 hours   Owner: Infrastructure / DevOps
medium
Software detected on tpg.com.sg has potential CVE matches. Review the specific CVEs and confirm whether the installed version is affected.
Remediation Steps
1
Review matched CVEs and confirm installed versions
2
Update software if vulnerable versions are confirmed
3
Consider hiding version information in server headers
4
Review certificate configuration
Effort: 1–2 hours   Owner: Infrastructure / DevOps
low
Certificate issues found for tpg.com.sg: 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
Security Headers
Critical
DMARC / Email Security
Warning
CVE Exposure
Warning
Certificate Hygiene
Warning
TLS Configuration
Healthy
DNS Configuration
Healthy
Known Breaches
Healthy
HSTS Header
Healthy