When to use a security assessment template
A security assessment is only useful if its findings get fixed. Many assessments end with a long report that sits in a folder while the same weaknesses remain. This template treats remediation and retesting as part of the project, so findings are tracked to closure with owners and dates.
Use it for a yearly security review, preparation for an audit or certification, a review after an incident or a first assessment for a small business. It suits managed service providers, security consultancies and internal IT teams.
How the template is structured
- Scope. Agree objectives, scope, rules of engagement and the framework, if any.
- Inventory. List assets, classify data and map access, including admin accounts.
- Assess. Review policies and controls, run vulnerability scans within the agreed rules and interview staff.
- Report. Rate findings by risk, write the report and present it.
- Remediate. Create one task per fix and address the highest risks first.
- Verify. Retest, update the risk register and schedule the next assessment.
Risk labels from Critical to Low keep the most important fixes at the top, and Accepted risk records conscious decisions not to fix something.
How to use it in Worklenz
- Create a project for the assessment and link the client if you are an MSP or consultancy.
- Add the phases and tasks above, then add a task per finding during reporting.
- Restrict access to the project to the people who need it, since findings are sensitive.
- Assign remediation owners and due dates based on risk.
- Track time on the Pro plan and above, separating assessment work from remediation.
Making security work visible and billable
MSPs often sell assessments at a fixed price and remediation as separate work. Tracking them separately with time tracking shows the real effort of each and supports accurate quotes. On the Business plan, project finance compares the budget with the cost of logged time.
Example: a yearly review for a small firm
An MSP runs a yearly security review for a 30-person accounting firm. The scope covers laptops, the cloud email and file platform, the website and backups. The inventory finds two former employees’ accounts still active, and scans find outdated software on several laptops.
The report rates the stale accounts as high risk and the missing multi-factor authentication on one admin account as critical. Remediation tasks are assigned to the MSP and to the firm’s office manager. Within two weeks, the critical and high findings are fixed and retested, one low-risk item is accepted, and the next review is scheduled.
Rating findings by risk
A simple risk rating keeps the report useful for both technical and business readers. Rate each finding on likelihood, how easy it is to exploit, and impact, how much harm it would cause, then combine them into one level. A missing security update on an internet-facing server is both likely and damaging, so it is critical. A weak setting on an internal test machine with no sensitive data is low. Explain each rating in one sentence, so business owners understand why one fix matters more than another, and agree target dates for each level, such as critical within days and high within weeks.
Who should be involved
A security lead owns the assessment and report. Engineers run scans and technical reviews. A business owner on the client side approves scope and accepts risks. System owners fix the issues found.
Common security assessment mistakes
The first mistake is testing without agreed rules of engagement. The second is a report with no owners or dates for fixes. The third is never retesting, so nobody knows whether fixes worked. This template covers all three.
Tips for better security assessments
- Agree rules before testing. Everyone should know what will happen and when.
- Start with access. Stale and over-privileged accounts are common, high-risk findings.
- Assign every finding. A finding without an owner is unlikely to be fixed.
- Retest and record. Closure needs evidence.
- Keep the report readable. A one-page summary for leadership gets fixes funded faster than a long technical appendix.
Related: the IT project template and the internal audit template.





