CyberBit Solutions
Cyber Risk Snapshot
Sample business: Harbor & Pine Dental
Domain reviewed: harborpinedental.example
Sample report
5/9
Medium Risk
Executive summary
This sample domain shows useful public-facing security signals, but several items are worth reviewing before relying on the setup for vendor, insurance, or client-trust conversations. The highest-value next step is to confirm who owns each setting, then clean up email authentication and website headers.
Top findings preview
Finding 01
DMARC policy needs enforcement review
- Observed
- A DMARC record was present in this sample, but the policy was set to monitoring mode instead of enforcement.
- Why it matters
- DMARC helps reduce fake emails that appear to come from the business domain. Monitoring is useful, but it may not stop spoofed mail by itself.
- Recommended fix
- Review SPF, DKIM, and legitimate senders first, then move toward a stronger DMARC policy with the email provider.
Finding 02
Website security headers need cleanup
- Observed
- The sample website responded over HTTPS, but several browser security headers were not returned in the public response checked.
- Why it matters
- Security headers can help reduce certain browser-based risks and make the website setup easier for a vendor or developer to review.
- Recommended fix
- Ask the website host, CDN, or developer to review HSTS, CSP, frame protection, MIME sniffing protection, Referrer-Policy, and Permissions-Policy.
Finding 03
Domain ownership and admin access should be documented
- Observed
- The sample intake indicated that domain, website, DNS, and email administration were split across multiple vendors.
- Why it matters
- When ownership is unclear, security fixes take longer and recovery is harder during a domain, email, or website incident.
- Recommended fix
- Document the domain registrar, DNS host, website host, email provider, admin contacts, and MFA status for each account.
Priority action plan
- 1Confirm who manages domain registration, DNS, website hosting, and business email.
- 2Review email authentication in order: SPF, DKIM, then DMARC.
- 3Ask the website host or developer to review missing website security headers.
- 4Save before-and-after evidence once public records or headers are updated.
- 5Use a Security Hardening Sprint if implementation help is needed after the Snapshot.
What this review includes
The Snapshot reviews public-facing website, email, and domain signals plus customer-provided context. It does not include logins, exploit testing, credential testing, or private-system access.
Optional next step: Security Hardening Sprint for implementation help.