Worklenz
Sign in
EN

Software & IT template

Security Assessment Template

Run a security assessment from scope to remediation: inventory assets, review risks and controls, test for vulnerabilities, report findings and track fixes to closure.

  • Free plan available
  • Open source (AGPL-3.0)
  • Cloud or self-hosted
Security analyst reviewing system risks

What's included in the Security Assessment template

phases
6
tasks
17
labels
5
statuses
3
1. Scope · 3 tasks
  • Agree objectives and scopeSystems, locations and processes in scope, the assessment type and the timeline.
  • Agree rules of engagementWhat testing is allowed, when, and who to contact if something goes wrong.
  • Identify the frameworkChoose the standard or checklist the assessment follows, if any.
2. Inventory · 3 tasks
  • List assetsDevices, servers, cloud services, applications and data stores.
  • Classify dataIdentify where sensitive and personal data is stored and processed.
  • Map accessReview who has access to key systems, including admin accounts.
3. Assess · 3 tasks
  • Review policies and controlsCheck password, access, backup, patching and incident response practices.
  • Run vulnerability scansScan systems in scope within the agreed rules of engagement.
  • Interview staffUnderstand how security works in practice, not only on paper.
4. Report · 3 tasks
  • Rate findings by riskRate each finding by likelihood and impact.
  • Write the assessment reportSummary for leadership, detailed findings and recommended fixes.
  • Present findingsWalk stakeholders through the risks and agree priorities.
5. Remediate · 2 tasks
  • Create remediation tasksOne task per fix, with an owner and due date based on risk.
  • Fix high-risk issues firstAddress critical and high findings before lower ones.
6. Verify · 3 tasks
  • Retest fixed issuesConfirm fixes work and close findings.
  • Update the risk registerRecord accepted risks and remaining actions.
  • Schedule the next assessmentSet the date for the next review, often yearly.

Labels

  • Critical
  • High
  • Medium
  • Low
  • Accepted risk

Who this template is for

  • Managed service providers and security consultancies assessing clients
  • Internal IT teams preparing for an audit or certification
  • Small businesses reviewing their security for the first time

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

  1. Scope. Agree objectives, scope, rules of engagement and the framework, if any.
  2. Inventory. List assets, classify data and map access, including admin accounts.
  3. Assess. Review policies and controls, run vulnerability scans within the agreed rules and interview staff.
  4. Report. Rate findings by risk, write the report and present it.
  5. Remediate. Create one task per fix and address the highest risks first.
  6. 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

  1. Create a project for the assessment and link the client if you are an MSP or consultancy.
  2. Add the phases and tasks above, then add a task per finding during reporting.
  3. Restrict access to the project to the people who need it, since findings are sensitive.
  4. Assign remediation owners and due dates based on risk.
  5. 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.

Start your security assessment project in Worklenz

Sign up free, then set up the phases and tasks above for your team.

Security Assessment template FAQs

What is a security assessment?

A structured review of an organisation's systems, data and practices to find security weaknesses, rate the risks and recommend fixes.

How often should a security assessment be done?

Many organisations run a full assessment once a year and after major changes, with lighter checks in between.

Is this security assessment template free?

Yes. The full template is on this page, and Worklenz's free plan includes task lists, kanban boards and built-in project templates.

Can remediation tasks be tracked in the same project?

Yes. Create one task per finding with a risk label, assign owners and due dates, and close each one after retesting.

Software & IT

Software Development template

Plan and deliver a software project in sprints: requirements, technical design, iterative development, testing, release and early support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Bug Tracking template

A simple bug tracking workflow: capture clear reports, triage and prioritise, fix with review, verify and close, then learn from patterns.

5 phases · 15 tasks. By Worklenz.

Software & IT

E-commerce Development template

Build or rebuild an online store: discovery, platform and design, product catalogue, checkout, payments and shipping, testing and a launch that protects sales.

6 phases · 19 tasks. By Worklenz.

Software & IT

IT Project template

Plan an IT project such as a system rollout, upgrade or migration: assess needs, plan and procure, implement, roll out to users and hand over to support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Data Migration template

Move data between systems safely: assess and map the data, clean it, run test migrations, cut over with a rollback plan and validate the results.

6 phases · 17 tasks. By Worklenz.

Software & IT

QA Testing template

Plan and run software QA: define scope and approach, write test cases, prepare environments, execute tests, track defects and sign off the release.

5 phases · 15 tasks. By Worklenz.

Explore more templates

Run your next project from a template

Worklenz is an open-source platform for agencies and service teams: projects, time tracking and client work in one place.