Client type
Hospitality / multi-site small business
A practical example of how Essetech reviews a small business environment, identifies risks, prioritises remediation, completes the work, and leaves the client with clear documentation.
Privacy note
De-identified case study. Client details, network information, and identifying data have been replaced with realistic sample information.
18
sample users
24
sample endpoints
10
deliverables
4
workflow stages
Capability demo
Built to show how findings can become practical fixes, clear estimates, and evidence a client can understand.
Case study snapshot
The sample scenario is intentionally ordinary: a busy small business with practical technology, inherited access, and documentation gaps that made security and support harder than it needed to be.
Client type
Hospitality / multi-site small business
Location
South Australia
Users
18
staff across shared and individual accounts
Devices
24
endpoints including laptops and shared workstations
Environment
Initial state
Ad-hoc IT support, limited documentation, inconsistent user access controls, unclear backup visibility.
Engagement type
Network review, Microsoft 365 clean-up, documentation, remediation plan, handover.
Outcome
Cleaner access control, clearer documentation, improved backup visibility, prioritised remediation plan, reduced operational risk.
What we found
Each item was written so a business owner, cyber adviser, or internal manager could understand the risk, the recommended action, and what evidence would be produced.
Risk
Some user accounts did not have consistent multi-factor authentication enforcement.
Business impact
Increased risk of account takeover, email compromise, invoice fraud, and unauthorised access.
Recommended action
Review all users, enforce MFA, confirm admin accounts are protected, and apply conditional access policies where licensing allows.
Evidence produced
User access summary, MFA status notes, screenshots of policy configuration, before-and-after remediation notes.
Risk
Administrative access was not clearly documented and some elevated permissions had not been recently reviewed.
Business impact
If an admin account was compromised, the attacker could gain broad access to systems, mailboxes, and business data.
Recommended action
Review global administrators, remove stale access, separate admin accounts from daily-use accounts, and document account ownership.
Evidence produced
Admin access register, removed-access summary, privileged account notes, handover recommendations.
Risk
Backups existed, but the scope, retention, alerting, and restore process were not clearly documented.
Business impact
The business could not confidently prove how quickly it could recover from accidental deletion, ransomware, device failure, or supplier issues.
Recommended action
Confirm backup scope, retention settings, alerting, restore process, and complete a sample restore test.
Evidence produced
Backup summary, restore test notes, screenshots where appropriate, gap list, next-step recommendations.
Risk
Devices, users, software, vendors, and key systems were not tracked in one central register.
Business impact
Harder to patch, secure, replace, support, quote, or investigate systems during an outage or incident.
Recommended action
Create a basic asset register covering devices, users, software, network equipment, vendors, warranties, and renewal dates.
Evidence produced
Asset register, device count, vendor list, support notes, renewal visibility.
Risk
The network layout, key devices, Wi-Fi configuration, vendor access, and support notes were not documented clearly.
Business impact
Support and incident response would be slower because the environment was dependent on memory rather than documentation.
Recommended action
Create a simple network diagram, document core devices, confirm access ownership, and record known support dependencies.
Evidence produced
Network summary, device list, support notes, simple topology diagram, handover document.
Risk
There was no clear checklist for creating users, assigning access, removing old users, or securing departed staff accounts.
Business impact
Old accounts could remain active, new users may receive incorrect access, and access control becomes harder to audit over time.
Recommended action
Create a lightweight onboarding/offboarding checklist and review inactive accounts.
Evidence produced
Checklist, inactive account summary, access review notes, recommended process.
Remediation workflow
The goal is not a bigger report. It is a clean list of decisions, fixes, evidence, and next steps.
Review network, Microsoft 365, users, devices, backup visibility, vendor access, and documentation gaps.
Sort findings by risk, business impact, urgency, effort, and cost so the client can make sensible decisions.
Fix MFA, admin access, backups, endpoint visibility, network documentation, vendor access, and support processes.
Provide clear documentation, evidence, screenshots where appropriate, recommendations, and a next-step roadmap.
Example before
Example after
Example deliverables
The handover is designed for support continuity, decision making, cyber review follow-up, and future quoting.
A plain-English summary of key devices, unknowns, risks, and support dependencies.
A user and access summary that highlights accounts needing review or remediation.
A clear record of privileged access and recommended changes.
A practical record of backup scope, retention, alerts, and restore test notes.
A central list covering devices, key systems, vendors, warranties, and renewals.
A prioritised task list showing what was fixed, deferred, or needs approval.
A scoped effort range that gives the client clear budget expectations.
A concise support reference covering systems, owners, access notes, and next steps.
A practical sequence for future security uplift and operational improvement.
Screenshots, configuration notes, and before-and-after details to support compliance or cyber review outcomes.
Risk to remediation tool
This sample interaction shows how Essetech can translate a finding into a scoped fix, evidence, and effort estimate.
MFA gap
Risk
User accounts may be exposed if credentials are reused, phished, or leaked.
Business impact
Email compromise, invoice fraud, unauthorised mailbox access, data exposure.
Fix
Review user MFA status, enforce MFA, protect admin accounts, and document exceptions.
Evidence produced
MFA status summary, configuration screenshots, user list notes, remediation record.
Estimated effort
2–5 hours
Example estimate preview
The estimate is practical and transparent: what is included, what is excluded, what evidence will be handed over, and the likely effort range.
Microsoft 365 Security Clean-up
Indicative range: $1,500–$3,500 + GST
Scope includes
MFA review
Admin account clean-up
User access review
Mailbox security check
Secure sharing review
Inactive account review
Baseline documentation
Handover notes
Indicative only. Final scope depends on tenant size, licensing, risk, and required evidence.
Project objective
Improve Microsoft 365 access control, reduce common account risks, and leave the client with evidence and clear handover notes.
Included tasks
MFA checks, admin review, inactive account review, mailbox baseline, secure sharing review, and documentation.
Exclusions
Licensing purchases, complex migrations, third-party security tooling, and unrelated endpoint remediation.
Estimated effort
8–16 hours depending on user count, licensing, tenant history, and evidence requirements.
Indicative range
$1,500–$3,500 + GST, subject to final scope approval.
Handover deliverables
Access review, configuration notes, before-and-after record, exceptions list, and recommended next steps.
Why this matters for cyber partners
Cyber assessments create the most value when the findings are remediated quickly, clearly, and with evidence. Essetech can help bridge the gap between advisory findings and completed technical actions.
Turns advisory findings into practical work items and completed actions.
Clear communication for clients who want practical local assistance.
Focuses on account control, access hygiene, secure sharing, and documentation.
Gives the client plain scope, effort, cost range, and exclusions.
Keeps notes, screenshots where appropriate, and before-and-after details.
Leaves future support teams with a useful operational reference.
Helps clients move from concern to action without being overwhelmed.
Creates a sensible path for maintenance, monitoring, and future improvements.
Prepared by Essetech
This de-identified case study shows how Essetech converts technical findings into scoped work, practical fixes, and client-ready documentation.
Prepared by Essetech as a de-identified capability demo. No client-sensitive information displayed.