- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Education · External test, segmentation validation and wireless review · Scoping brief
A residential college with 200 unmanaged student devices.

Scoping brief. How this engagement was scoped.
- Organization
- Australian residential college
- Stage
- Scoping brief
- Sector
- Education
- Service
- External test, segmentation validation and wireless review
The situation
Around 200 resident-owned devices share a network with staff systems that hold personal information.
The college has a small team and an outside IT contractor.
How we scoped it
- The priority is separation, not just the perimeter
- Testing starts from the resident network and documents exactly what can be reached from there
- Delivery is remote, through a small virtual machine or a shipped device
- The IT contractor is involved from the first call
Planned deliverables
- External findings
- Segmentation results
- Wireless review
- Prioritized fix list
How a GuardsArm penetration test runs
- Scope and rules of engagementTargets, testing windows, out-of-scope systems and emergency contacts are agreed in writing before any traffic is sent.
- Reconnaissance and mappingWe map what is actually reachable: hosts, services, applications and identities, including anything the asset list missed.
- Testing and exploitationFindings are confirmed by hand, not copied from a scanner. Exploitation stays inside the agreed rules and stops before it risks production.
- ReportingAn executive summary for the people who fund the fixes and a technical report for the people who make them, each finding with evidence and a remediation path.
- RetestAfter remediation we retest the findings and confirm in writing which are closed, so the report can be used as evidence.
Standards we work to
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessment
- OWASP Web Security Testing Guide (application and API testing)
- Penetration Testing Execution Standard (PTES)
- CVSS for finding severity
Questions buyers ask
What does a penetration test cover?
Whatever the scope says, and nothing else. GuardsArm tests external, internal, application and wireless environments against rules of engagement agreed before testing starts.
Will testing disrupt our systems?
Testing windows, rate limits and any fragile systems are agreed up front. Anything that could affect production is discussed before it is attempted, not after.
What do we receive at the end?
An executive report and a technical report. Each finding has evidence, a severity, and a remediation path your team can act on.
Is a retest included?
GuardsArm retests after remediation and confirms in writing which findings are closed, which is what auditors and insurers usually ask to see.
The service behind this work
Penetration testing
External, internal, application and wireless testing with executive and technical reporting and a retest.
Further reading
Penetration Testing
Advanced Penetration Testing MethodologiesPenetration Testing
Building a Penetration Testing Methodology and FrameworkPenetration Testing
IoT Device Penetration Testing for Connected Devices
Take it with you
Download this scoping brief as a PDF
The same account in a designed 5-page document, with how GuardsArm runs this kind of engagement and the questions buyers ask. Useful for sharing with your leadership or procurement team.
- Instant download
- A copy by email
- No spam