Chapter 3. Target Scoping
Prior to conducting any type of penetration test, the pentester needs to engage the client to ensure that all the appropriate information is obtained. During the target scoping phase, the penetration tester will gather information from the client that will be used to generate target assessment requirements, define the parameters for testing, and the client's business objectives and time schedule. This process plays an important role in defining clear objectives toward any kind of security assessment. By determining these key objectives, one can easily draw a practical road map of what will be tested, how it will be tested, what resources will be allocated, what limitations will be applied, what business objectives will be achieved, and how the test project will be planned and scheduled. All of this information is finally captured in a test plan that expressly states what the scoping of the test will be.
We can combine all of these elements and present them in a formalized scope process to achieve the required goal. The following are the key concepts that will be discussed in this chapter:
- Gathering client requirements: This deals with accumulating information about the target environment through verbal or written communication.
- Preparing the test plan: This depends on different sets of variables. These variables may include shaping the actual requirements into a structured testing process, legal agreements, cost analysis, and resource allocation.
- Profiling test boundaries: This determines the limitations associated with the penetration testing assignment. These can be a limitation of technology, knowledge, or a formal restriction on the client's IT environment.
- Defining business objectives: This is a process of aligning business views with the technical objectives of the penetration testing program.
- Project management and scheduling: This directs every other step of the penetration testing process with a proper timeline for test execution. This can be achieved using a number of advanced project management tools.
It is highly recommended that you follow the scoping process in order to ensure test consistency and a greater probability of success. Additionally, this process can also be adjusted according to the given situation and test factors. Without any such process there will be a greater chance of failure, as the requirements gathered will have no proper definitions and procedures to follow. This can lead the entire penetration testing project into danger and may result in an unexpected business interruption. At this stage, paying special attention to the penetration testing process would make an excellent contribution toward the rest of the test phases and clear the perspectives of both technical and management areas. The key is to acquire as much information as possible from the client beforehand to formulate a strategic path that reflects the multiple aspects of penetration testing. These may include negotiable legal terms, contractual agreement, resource allocation, test limitations, core competencies, infrastructure information, timescales, and rules of engagement. As a part of best practices, the scope process addresses each of the attributes that are necessary to initiate our penetration testing project in a professional manner.
Each step constitutes unique information that is aligned in a logical order to pursue the test execution successfully. This also governs any legal matters to be resolved at an early stage. Hence, we will explain each of these steps in more detail in the following section. Keep in mind that it will be easier for both the client and penetration testing consultant to further understand the process of testing if all the information gathered is managed in an organized manner.
- 零基礎(chǔ)學(xué)C++程序設(shè)計
- Learning Chef
- 程序員面試算法寶典
- Responsive Web Design with HTML5 and CSS3
- PostgreSQL Replication(Second Edition)
- Visual C#.NET程序設(shè)計
- 深度學(xué)習(xí):Java語言實現(xiàn)
- Unity 2017 Mobile Game Development
- 深入淺出React和Redux
- Spring Boot+MVC實戰(zhàn)指南
- Django 3.0應(yīng)用開發(fā)詳解
- PrimeFaces Blueprints
- 深度實踐KVM:核心技術(shù)、管理運維、性能優(yōu)化與項目實施
- 計算機應(yīng)用基礎(chǔ)案例教程(第二版)
- Socket.IO Cookbook