Prepared by NetAssist (M) Sdn Bhd
Security assessment guide
The scope decides what a penetration test can tell you, so agree it in writing before you compare quotes. This guide draws on the UK National Cyber Security Centre (NCSC), the US National Institute of Standards and Technology (NIST), cloud providers’ own testing rules and Malaysia’s regulators. At NetAssist, a Malaysian managed security service provider, penetration testing is one of our security assessment services.
Published 5 November 2026
- The UK NCSC says scoping a penetration test should involve all relevant risk owners, technical staff who know the target system and a representative of the penetration test team.
- NIST SP 800-115 says an assessment plan should list the systems that are not authorised for testing, at a minimum by IP address and preferably also by system name.
- NIST says the owner of a third-party network that houses your systems usually must also consent in writing to the assessment plan.
- AWS lets customers test their own AWS infrastructure without prior approval for the services it lists, but not AWS infrastructure or the AWS services themselves.
- NACSA’s licensing FAQ says a subcontractor that provides a cyber security service on behalf of the main contractor is required to be licensed.
Agree a written scope with your risk owners, your technical staff and the testers before testing starts. It should name the systems in scope and the ones excluded, the types of test, the timeframe and effort, what the testers need from you, any compliance and reporting requirements and, where some of your systems are housed on someone else’s network, that owner’s written consent, which NIST says is usually needed.
On this page9
Who should be involved in scoping a penetration test?
Three groups should be in the room. The UK NCSC’s penetration testing guidance says scoping should involve all relevant risk owners, technical staff knowledgeable about the target system and a representative of the penetration test team. Each brings something the others cannot: the business concerns, the real technical boundaries and a view of what testing will give a full picture.
In the NCSC’s model, risk owners outline areas of special concern, technical staff outline the technical boundaries of the IT estate, and the test team proposes the testing. If you have a current vulnerability assessment, the NCSC says to share it with the testers at this stage. Raise unusual systems, such as mainframes or bespoke hardware, in the bid process so that providers know which skills the work needs.
What should be in scope, and what should be left out?
List both. NIST SP 800-115 says an assessment plan should identify which systems and networks are authorised for testing, for example by the number of systems and their IP addresses or address ranges, and should also list the systems that are not authorised, at a minimum by IP address and preferably also by system name. NIST’s rules of engagement template calls this the exclude list.
NIST’s example is a payroll database judged too mission-critical for a particular type of test. It also says assessors given a list of public IP addresses should verify that they are under the organisation’s purview before testing begins, and that the plan should state prohibited activities, such as file creation and modification, in a way that leaves no room for interpretation. The NCSC adds that scoping should raise anything that might affect testing, such as out-of-hours testing or critical systems needing special handling.
“A well-scoped penetration test can give confidence that the products and security controls tested have been configured in accordance with good practice and that there are no common or publicly known vulnerabilities in the tested components, at the time of the test.”– UK National Cyber Security Centre, Penetration testing
How much should the testers be told?
It depends on what you want to learn. The NCSC describes open box testing, where full information about the target is shared with the testers, and closed box testing, where none is shared. Closed box testing models an outside attacker more closely, but the NCSC warns that the lack of information can leave vulnerabilities undiscovered in the time allocated for testing.
A test can also be built around scenarios. The NCSC suggests choosing them based on previous incidents, with examples such as a lost laptop, an unauthorised device connected to the internal network and a compromised DMZ host. If the test should also check whether your monitoring team or managed SOC notices the activity, say so in the scope. NIST says the plan should identify the IP addresses the testers will work from, so administrators can tell test activity from a real attack.
Should you test live systems or a copy?
Decide it per system and write it down. NIST says organisations should consider whether to test production systems or similarly configured non-production systems, or restrict certain techniques to off-hours, to minimise impact on operations. A copy is safer, but NIST notes that test and production environments usually differ, which can result in missed vulnerabilities.
Where testing could expose sensitive personal data, NIST suggests considering a non-production system holding test data instead of the real records. Whichever you choose, plan for the unexpected: the NCSC says unexpected reactions to testing cannot be ruled out, and that a technical point of contact should be available at all times during the test. NIST’s rules of engagement template asks for criteria for halting the testing.
What about cloud and third-party hosted systems?
Check whose permission you need before they go in scope. NIST says that when part of your network is housed on a third party’s network, the owner of that network usually must also consent in writing to the assessment plan. Cloud providers publish their own rules, which bind the testers you hire as well as you.
The AWS penetration testing policy says customers may test their AWS infrastructure without prior approval for the services it lists, does not permit any assessment of AWS infrastructure or the AWS services themselves, and lists denial of service among its prohibited activities. It also makes the customer responsible for ensuring that contracted third parties follow the policy. Microsoft’s security testing rules of engagement apply equally to the owner of a resource and its authorised agents, and prohibit denial-of-service testing. Check the current rules of every provider in scope.
What should the written scope say?
The written scope should leave nothing to guesswork. The NCSC lists what the output of scoping should state, from the technical boundaries and types of test to reporting requirements, and NIST adds the exclude list, the IP addresses the testers will work from and a signature page. NIST defines rules of engagement as “Detailed guidelines and constraints regarding the execution of information security testing.”
| Item | What to write down | Source |
|---|---|---|
| Boundaries | The technical boundaries of the test, and the systems excluded from it | NCSC; NIST |
| Test types | The types of test expected, and any scenarios or use cases | NCSC |
| Time and effort | The timeframe and the effort needed, usually given in resource days | NCSC |
| Tester requirements | What the testers need from you, such as test accounts | NCSC |
| Compliance | Any compliance or legislative requirements the testing plan must meet | NCSC |
| Reporting | Specific reporting requirements, such as CVSS scores | NCSC |
| Halting and contacts | Criteria for halting the testing and the contacts to call | NIST |
| Sign-off | The test team leader and senior management sign that they understand the scope and boundaries | NIST |
NIST says the plan should be followed unless permission to deviate is obtained, normally in writing, from the original signatory. Our guide to what a penetration test report should contain covers the reporting side.
What do Malaysian rules add to the scope?
Two things to check. NACSA’s licensing FAQ names penetration testing as a service that must be licensed, and says a subcontractor that provides the service on behalf of the main contractor is required to be licensed too. Its definition of a penetration testing service also includes using social engineering, so decide whether that is in your scope.
The FAQ describes the Cyber Security (Licensing of Cyber Security Service Provider) Regulations 2024 [P.U. (A) 221/2024]. For the financial institutions it covers, Bank Negara Malaysia’s RMiT policy document (issued 25 September 2026, Appendix 5, Part D) requires procedures that include “ensuring that the activities of external penetration testers are within the defined scope and are always subject to continuous oversight”. It also requires annual intelligence-led penetration tests on internal and external network infrastructure, critical systems and digital services. How these rules apply to your organisation is a question for your own advisers.
At NetAssist, we hold NACSA licences for penetration testing and managed SOC monitoring, and we customise the scope and methodology of our penetration tests to your business environment, across web, mobile, API, cloud, internal, external, wireless and network assessments. See our security assessment and consultancy services, or our guide to choosing between a penetration test or a vulnerability assessment.
FAQ
What happens if testers find a system outside the scope?
The NCSC says the testers may suggest a change to the scope, which is likely to alter the time frames and cost, or recommend that the exclusion be recorded as a limitation on testing. The decision will generally be down to the risk owner.
Should we share our latest vulnerability assessment with the testers?
Yes, if you have a current one. The NCSC says a current vulnerability assessment should be shared with the testers at the scoping stage, so the testing can support a view on how accurate and complete your own assessment is.
Do we need our cloud provider’s permission to run a penetration test?
It depends on the provider and the service. AWS lets customers test their AWS infrastructure without prior approval for the services it lists, but not AWS’s own infrastructure or services. NIST says the owner of a third-party network housing your systems usually must consent in writing.
How is the length of a penetration test agreed?
At scoping. The NCSC says the scoping document should state the timeframe and the amount of effort needed to deliver the testing, usually given in resource days, along with any time constraints on testing or reporting.
Sources
- Penetration testing, UK National Cyber Security Centre, reviewed 10 January 2022 (opened 6 Nov 2026)
- NIST SP 800-115: Technical Guide to Information Security Testing and Assessment, US National Institute of Standards and Technology, September 2008 (opened 6 Nov 2026)
- Licensing of Cyber Security Service Provider FAQ, National Cyber Security Agency (NACSA) Malaysia (opened 6 Nov 2026)
- Risk Management in Technology (RMiT) policy document, Bank Negara Malaysia, issued 25 September 2026 (opened 6 Nov 2026)
- Penetration Testing, Amazon Web Services (opened 6 Nov 2026)
- Microsoft Security Testing Rules of Engagement, Microsoft Security Response Center (opened 6 Nov 2026)
Planning a penetration test?
Tell us which systems and applications you want tested, what must stay out of scope and what the report needs to show. We will shape the scope and methodology around your business environment.

