Review the current position
Define the controls and systems to examine, the access needed and the evidence available. Record gaps in information alongside the findings so decision-makers can see the assessment’s limits.
IT services
A cyber security assessment should help you understand the gaps in an agreed part of your environment and decide what to address next. Subnet can help assess the current position, interpret findings and shape a prioritised improvement plan. Remediation and verification are scoped to the work you approve.
WORK WITH SUBNET
A finding needs a next step. Subnet helps you prioritise the issues that matter to your environment, agree the changes to make and record how those changes will be checked. Remediation can be delivered as a defined project or allocated between your internal team, Subnet and other providers.
The scope should identify the affected systems, dependencies, approval points and verification criteria. Unresolved findings and accepted exceptions remain visible, rather than disappearing when the report is delivered. An assessment does not automatically include every fix, and a successful retest does not establish whole-framework compliance.
WORK WITH SUBNET
Active Directory often carries years of changes to accounts, groups, permissions and configuration. A focused review can help identify where that history has created uncertainty, operational issues or unnecessary access.
Subnet can discuss an assessment of the agreed directory environment and help turn the findings into a prioritised remediation plan. Changes should take account of application dependencies, service accounts and recovery arrangements, with approval and verification built into the work.
Active Directory Domain Services is distinct from cloud-only Microsoft Entra ID. The assessment scope and any remediation must be agreed for your environment.
WORK WITH SUBNET
A cloud-security platform needs an agreed policy baseline, pilot and handover approach. Subnet’s scoped Netskope SSE work includes tenant hardening, traffic steering, SSL inspection, web security and CASB policy.
Full DLP programme design and Private Access design are separate from that baseline. Define the required capabilities, licensing, change responsibilities and verification before implementation.
WORK WITH SUBNET
Taking over an environment can reveal configuration gaps that need a project alongside ongoing support. Subnet can turn selected onboarding findings into a defined set of changes, with priorities, owners and verification agreed for each item.
Depending on the findings, work may address specified identity or cloud settings, firewall configuration standardisation, reporting gaps or other agreed configuration issues. The scope should identify the affected systems and distinguish Subnet's work from actions retained by your team or another provider.
Onboarding does not include unlimited remediation. Disaster recovery exercises, major platform upgrades and privileged-access projects need separate agreement where required. Outstanding issues and next steps should remain clear at handover.
WORK WITH SUBNET
Understand the tenant, existing entitlements and operational responsibilities before prioritising identity, email, endpoint and administrative controls. Subnet can scope selected security-feature enablement and configuration changes, with testing and handover.
Separate lower-impact settings from changes that affect sign-in, applications or user workflows. High-impact changes need approval, exceptions and a recovery approach. Microsoft Secure Score can support a review; it is not a certification or a guarantee of security.
Defender product plans cover different workloads and capabilities. Endpoint EDR, email protection, server coverage and ongoing alert response must be explicitly selected. Purview classification and wider governance programmes are separately scoped.
You may need to review an existing set of controls, understand findings from testing or decide which improvements deserve attention first. An assessment is more useful when its purpose is specific enough to guide the scope and the evidence required.
Identify the systems, users, sites or business services involved. Agree whether the work is a technical review, a review against a selected framework, a policy and process review, or a combination. A report about one part of the environment should not be read as assurance about everything else.
Define the controls and systems to examine, the access needed and the evidence available. Record gaps in information alongside the findings so decision-makers can see the assessment’s limits.
Translate results into issues the organisation can act on. Consider the affected service, exposure, dependencies and practical options for treatment rather than relying on a technical severity label alone.
Set out the recommended actions, proposed owners and the decisions needed before work starts. Some changes may be operational tasks; others may need a separate project, budget or third-party involvement.
Agree what evidence will show that a change has been completed and whether a finding needs retesting. Keep unresolved items and exceptions visible, with an owner and an agreed next step.
A configuration review checks settings against agreed criteria. A vulnerability assessment identifies and analyses weaknesses in the systems under review. A penetration test uses authorised attack scenarios to explore whether a defined objective can be achieved. Specify the method, targets, access, exclusions and handling of results before testing begins.
Penetration testing may be delivered with a specialist third party, with Subnet providing analysis and remediation planning. The proposal should identify the delivery roles and testing boundaries. Do not assume that every assessment includes penetration testing or permission to test every connected system.
Read the Australian Cyber Security Centre’s guidance on security assessments How the Australian Cyber Security Centre defines a penetration testIllustrative example: an organisation wants a clearer view of privileged access across a defined group of systems.
The scope identifies the systems and the people who can authorise access to the evidence. The review records the current arrangements and the gaps against the agreed criteria. Findings are grouped by their implications and dependencies, then assigned to a decision-maker or delivery owner.
Approved changes are implemented through the organisation’s change process. Verification checks are recorded against the original findings, while exceptions remain in the action list. Measures could include findings with an agreed treatment, completed verification checks and unresolved items with named owners.
This example shows how the work could be structured. It is not a customer outcome or a claim that a particular control set removes all risk.
The engagement should distinguish assessment, implementation and verification. A finding does not itself authorise a system change, and an assessment fee does not automatically include all remediation.
Subnet’s NCVER case study describes work on security fundamentals, policy creation, incident-response planning and ongoing maturity assessment.
Read the NCVER case studySubnet’s published Turner Real Estate case study describes an assessment of systems and workflows, a tailored security strategy, and staff cyber-awareness training.
Some findings can be closed through a defined change. Others need continued ownership, maintenance or monitoring. The handover should make that distinction clear and identify who will keep the arrangements current.
If you need an ongoing managed security service, explore +Security. Its coverage, action authority and remediation responsibilities should be agreed separately from a one-off assessment or project.
+Security managed securityPenetration testing is one type of security assessment. A broader engagement might review controls, configurations or processes as well. Confirm whether testing is included, its authorised targets and what the findings can establish; the word “assessment” alone does not define the method.
Discuss the framework or benchmark relevant to the decision you need to make. Confirm the systems covered, assessment criteria, evidence requirements and any exclusions. A framework reference alone does not establish certification or a compliance outcome.
Remediation is separately scoped and approved. The findings should help you decide priorities, identify dependencies and allocate owners. Some work may sit with your internal team or another provider, and some may need a separate implementation project.
A testing engagement may use a specialist third party, with Subnet analysing the findings and helping plan remediation. Confirm the delivery team, testing method, authorisation and reporting arrangements in the proposal.
Agree verification criteria before implementing the change. Depending on the finding, that may involve reviewing configuration evidence, repeating a check or commissioning a retest. Record the result and any remaining exceptions against the original action.
A one-off assessment or project and an ongoing service serve different purposes. Discuss who will maintain the controls and handle ongoing security work after the engagement. +Security can be considered separately where a managed service is appropriate.
Start with the decision the assessment is meant to inform. Then agree what is in scope: the systems, users, sites or business services involved, and whether the work is a technical review, a review against a selected framework, a policy and process review, or a combination. Also settle the evidence to be reviewed, the access and permissions to be granted, any exclusions, who will provide subject-matter input and who the report is for. A report on one part of the environment should not be read as assurance about everything else.
The output should turn technical results into issues your organisation can act on, considering the affected service, exposure, dependencies and treatment options rather than relying on a severity label alone. It should set out recommended actions, proposed owners and the decisions needed before work starts, and record gaps in the information reviewed so the limits of the assessment are visible. The format and level of detail are agreed in the proposal.
The Essential Eight is the Australian Signals Directorate’s set of mitigation strategies, covering areas such as patching, multi-factor authentication, restricting administrative privileges, application control and backups, with maturity levels describing how fully they are implemented. In June 2026, ASD consulted on evolving the Essential Eight into a wider Essentials series, with a proposed first chapter called Essentials for enterprise IT. If you want either used as the reference point, agree which ASD document and version applies, the systems in scope and the evidence required, and check ASD’s current guidance on cyber.gov.au. Using a framework as a reference does not make an assessment a certification.
Reassessment should follow the findings rather than a fixed calendar interval. Verifying an approved change may need only a repeated check or retest of that finding. A wider reassessment is worth considering after significant changes to systems, suppliers or the people responsible, or when the framework or guidance you used as a reference is updated. Keep unresolved items and accepted exceptions on the action list with an owner so they are revisited. A successful retest does not establish whole-framework compliance, and ongoing monitoring needs its own agreed arrangement.
EXPLORE FURTHER
BEFORE WE TALK
You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.
LET’S TALK
Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.