CyberSafe SWLOCAL KNOWLEDGE. DIGITAL CONFIDENCE.
A CLEAR PICTURE. A USEFUL DELIVERABLE.

This is what
clarity looks like.

A fictional example of the findings and recommendations an assessment report can include. Actual reports depend on the agreed scope and package.

SAMPLE REPORT — FOR ILLUSTRATION ONLY
01 · EXECUTIVE SUMMARY

Cyber Security Check-Up

Example environment: a fictional small business with one reviewed Windows computer, a primary email account, Wi-Fi and existing backup arrangements.

This example highlights useful existing protections and practical areas to improve. The priority labels describe recommended attention, rather than a security score or certification.

2! Action recommended
2↗ Worth reviewing
2✓ Looking good

What matters most: enable an extra sign-in check on the primary email account and review administrator access. Then verify backup recovery and guest Wi-Fi separation.

02 · WHAT WE CHECKED

Six areas. A defined scope.

Area reviewedExample scope
Email sign-inTwo-factor authentication and recovery arrangements.
Windows account accessEveryday account type and administrator privileges.
Backup & recoveryConfigured backups and evidence of file recovery.
Wi-Fi arrangementsGuest access and separation from work devices.
Operating system updatesAutomatic update setting and visible update status.
Device protectionEnabled protection and reported definition status.

Not reviewed: penetration testing, all cloud settings, every device, compliance certification or historical incident analysis.

03 · FINDINGS & PRIORITIES

What needs attention.
What’s looking good.

! Action recommended · F01

Protect the primary email account

What we observed
Two-factor authentication is not enabled on the fictional primary email account.
Why it matters
A person with the password may be able to sign in without a second check. Email access can also affect password resets for other accounts.
Recommended action
Enable a supported sign-in method, preferably a phishing-resistant option where available. Check recovery details and store recovery codes safely.
! Action recommended · F02

Separate everyday and administrator access

What we observed
The fictional everyday Windows account has administrator privileges.
Why it matters
Administrator access allows broad changes to a computer. Using it for routine work increases the potential impact of an unwanted action.
Recommended action
Discuss using a standard account for daily work and a separate administrator account for authorised changes. Confirm application needs before changing access.
↗ Worth reviewing · F03

Verify that files can be recovered

What we observed
Backups are configured, but successful file recovery has not been verified.
Why it matters
A backup schedule alone does not show whether the right files are covered or whether you could restore them.
Recommended action
With permission, restore a non-sensitive test file to a separate location. Check the contents, date and backup coverage. Record the result.
↗ Worth reviewing · F04

Review guest Wi-Fi arrangements

What we observed
The fictional guest Wi-Fi network uses the same network as work devices.
Why it matters
Visitors may be connected to the same network as business devices. Available separation depends on the router and its configuration.
Recommended action
Review a separate guest network where supported. Confirm business requirements and test connectivity before making changes.
✓ Looking good · F05

Keep automatic updates enabled

What we observed
Automatic operating system updates are enabled on the reviewed fictional computer.
Why it matters
The setting supports receiving updates, but it does not prove every application is current or that all future updates will succeed.
Recommended action
Keep the setting enabled and periodically check update history, restart requirements and relevant applications.
✓ Looking good · F06

Maintain device protection

What we observed
Built-in device protection is enabled and reports current definitions in the fictional example.
Why it matters
This is a useful basic protection. Its reported state is not proof that malware or other threats are absent.
Recommended action
Keep protection enabled. Review any warnings and continue safe account, update and backup practices.
04 · RECOMMENDED NEXT STEPS

A sensible order of action.

  1. Start with account access. Enable supported two-factor authentication and review administrator use with the account owner.
  2. Test recovery safely. Restore a test file to a separate location and confirm important files are covered.
  3. Review the network. Check guest Wi-Fi options and agree changes before interrupting connectivity.
  4. Maintain what is working. Keep updates and device protection enabled and review their status regularly.

Agree an owner for each action and a review date that suits the environment. Implementation is separate from this example assessment unless explicitly included in the service.

05 · SCOPE & LIMITATIONS

A snapshot, with clear boundaries.

All information here is fictional. This is a marketing example and does not describe a real customer, device, account, visit or assessment result.

A Cyber Security Check-Up is a point-in-time review of agreed areas, subject to available access and evidence. It cannot establish complete security, detect every threat, or guarantee future outcomes. It is not a formal certified audit or compliance certification.

Checks and reporting depend on the environment and agreed package. Changes, recovery tests and additional work require suitable permission and an agreed scope. No proprietary toolkit code or scoring methods are included.

SAMPLE REPORT — FOR ILLUSTRATION ONLY · CyberSafe SW

LET’S START WITH A CONVERSATION

Not sure where your
security stands?

Tell Josh what you’re concerned about.
We’ll help you work out the next step.

Contact JoshExplore the Check-Up