# Security remediation [Read the public page](https://www.adarkcloud.com.au/services/security-remediation) Turn agreed security findings into checked changes. Perth based remediation help for small businesses, with remote work across Australia. Security remediation addresses identified weaknesses through agreed updates, configuration changes or other treatment. We review the evidence and dependencies, scope the work and check the result. Perth based support is available for suitable remote changes across Australia. Perth based, with remote support across Australia. From $79 an hour ex GST, with the fee agreed before work begins. Call Josh C on 0408 530 303. ## What we can help with - Finding and dependency review - Approved remediation plan - Scoped configuration or update work - Relevant completion checks - Remaining risk and handover notes An audit or scan can leave you with a report and no clear route to completing the work. The first step is to establish which findings apply, what access is available and who can authorise a change. We can scope a defined set of findings without assuming that the report covers the whole environment. ## Start with the finding and its evidence Bring the report, affected system and any deadline or requirement attached to it. We review what was checked, when it was checked and whether the finding still applies. A scanner's recommendation may need validation before a live change. A missing update, an exposed service and an overly broad permission involve different responses and different acceptance checks. ## Agree on the change and who approves it The remediation plan identifies the proposed action, affected users and the person authorised to approve it. We establish whether another provider or software vendor needs to participate. Fees and dependencies are agreed before implementation. If access is incomplete or a system is unsupported, the scope should explain the consequence rather than assume the change will be straightforward. ## Protect the work while settings change A security change can interrupt a line of business app or remove access someone needs. We discuss timing, recovery options and a relevant working test before making the change. The review may identify a need for a backup or a vendor check first. Those prerequisites belong in the plan, especially when the system has limited recovery options. ## Use a workaround with a defined purpose Where an update is unavailable, restricting access or disabling affected functionality may reduce exposure. A workaround should be documented as a temporary treatment rather than a permanent fix by default. The business needs to understand which use is affected and which risk remains. The record should name who follows up the vendor response or longer term replacement. ## Verify the result against the original issue Completion evidence should address the finding that prompted the change. A follow up scan, configuration check or functional test may be appropriate, depending on the system and scope. We record what changed and which checks passed. A successful check of one finding does not establish that unrelated weaknesses or excluded systems have also been addressed. ## Leave a usable handover The handover identifies completed work, unresolved dependencies and the person responsible for each remaining item. Ongoing patching or monitoring needs its own agreement if it was not included. Remote implementation can suit businesses anywhere in Australia. Perth site work, physical replacement and specialist incident response are separate requirements to establish during scoping. ## Common questions ### Can you work from another provider's report? Yes. We review its scope, evidence and current relevance before quoting changes. Any unclear or disputed finding needs to be resolved rather than implemented blindly. ### Is remediation included in a vulnerability review? Only when the agreed scope includes it. Finding a weakness and implementing a change are separate responsibilities, with access, cost and acceptance checks established for each. ### Who accepts a risk that cannot be fixed immediately? An authorised person in your business makes that decision. We document the remaining issue, possible treatment and review point so the decision has a clear basis. ### Can you remediate an active incident? An active compromise needs incident handling and may require a specialist responder. Explain that situation first so routine improvement work is not mistaken for incident response. ## Useful next steps - [Vulnerability management](https://www.adarkcloud.com.au/services/vulnerability-management) - [Patch management](https://www.adarkcloud.com.au/services/patch-management) - [Microsoft 365 security](https://www.adarkcloud.com.au/services/microsoft-365-security) - [Backups and recovery](https://www.adarkcloud.com.au/services/backups-and-security) - [ASD guidance on patching applications and operating systems](https://www.cyber.gov.au/business-government/protecting-devices-systems/system-administration/patching-applications-and-operating-systems) - [Small business IT health check](https://www.adarkcloud.com.au/tools/it-health-check) Reviewed 2026-10-08 - [Ask for IT help](https://www.adarkcloud.com.au/contact) - [Check your IT basics](https://www.adarkcloud.com.au/tools/it-health-check)