1. Preparation
   1. Introduction
      1. Testing organisation history and background.
      2. Authority to test i.e. Request from company, corporate headquarters or potential buyer of company.
      3. Detailed Proposal of test and services that are proposed to be carried out.
      4. Capability Statement of the testing organisation i.e Core competencies/ limitations/ timescales etc.
      5. Tools to be utilised if requested.
   2. Accreditation Status
      1. Interim
      2. Re-accreditation
      3. Full
   3. Scope of Test
      1. Stage of Lifecyle
         1. Interim Operating Capability i.e. Development build/ beta stage.
         2. Final Operating Capability i.e. Project at customer acceptance stage.
         3. Major upgrade i.e. Software/ hardware update.
      2. Test Type
         1. Compliance Test
            1. Basically an audit of a system carried out against a known criterion. A compliance test may come in many different forms dependant on the request received but basically can be broken down into several different types:
            2. Operating Systems and Applications: A verification that an operating system and/or applications are configured appropriately to the companies needs and lockdown requirements, thus providing adequate and robust controls to ensure that the Confidentiality, Integrity and Availability of the system will not be affected in its normal day to day operation.
            3. Systems in development: A verification that the intended system under development meets the configuration and lockdown standards requested by the customer.
            4. Management of IT and Enterprise Architecture: A verification that the in-place IT management infrastructure encompassing all aspects of system support has been put in place. This is to ensure effective change control, audit, business continuity and security procedures etc. have been formulated, documented and put in place.
            5. Interconnection Policy: A verification that adequate security and business continuity controls governing the connection to other systems, be they Telecommunications, Intranets, Extranets and Internet etc. have been put in place, have been fully documented and correspond to the stated customer requirements.
            6. Full credentials Supplied
            7. Full access to Network diagrams and schematics
            8. Full access to Configuration scripts and files
            9. Compliant with:
            10. Customer Defined
            11. Government Assurance Pack
            12. HIPAA
            13. ISO27001
            14. Microsoft Lockdown
            15. NSA Lockdown
            16. Sorbanes Oxley
            17. Etc.
         2. Vulnerability Assessment
            1. Vulnerability assessment is a process of identifying and analysing a system or network for any potential vulnerabilties, flaws or weaknesses that could leave it open to exploitation.
            2. Full credentials Supplied or limited to basic user credntials dependant on level of test
            3. Full access to Network diagrams and schematics
            4. Full access to Configuration scripts and files
         3. Penetration Test
            1. A Penetration Test is essentially an evaluation of a system or networks current state of security and its likelihood to be susceptible to a successful attack by a malicious hacker or nefarious user. The process involves enumeration and scanning for any technical flaws or vulnerabilities. After such flaws are found, attempts are then made to penetrate inside the network and gain a foothold. Once this has been established, attempts are then made to utilise trusts and relationships to gain further ingress into the domain.
            2. Type of Test
            3. White-Box
            4. The testing team has complete carte blanche access to the testing network and has been supplied with network diagrams, hardware, operating system and application details etc, prior to a test being carried out. This does not equate to a truly blind test but can speed up the process a great deal and leads to a more accurate results being obtained. The amount of prior knowledge leads to a test targeting specific operating systems, applications and network devices that reside on the network rather than spending time enumerating what could possibly be on the network. This type of test equates to a situation whereby an attacker may have complete knowledge of the internal network.
            5. Black-Box
            6. No prior knowledge of a company network is known. In essence an example of this is when an external web based test is to be carried out and only the details of a website URL or IP address is supplied to the testing team. It would be their role to attempt to break into the company website/ network. This would equate to an external attack carried out by a malicious hacker.
            7. Grey-Box
            8. The testing team would simulate an attack that could be carried out by a disgruntled, disaffected staff member. The testing team would be supplied with appropriate user level privileges and a user account and access permitted to the internal network by relaxation of specific security policies present on the network i.e. port level security.
            9. Exclusions
            10. Social Engineering Attacks
            11. Denial of Service Attacks etc.
            12. See also Exemptions from test section.
         4. Purpose of Test
            1. Deployment of new software release etc.
            2. Security assurance for the Code of Connection
            3. Interconnectivity issues.
            4. Deployment of wireless networks on wired LAN.
            5. ISO27001/HIPAA etc. Compliance
   4. Obtain appropriate Network details (dependant on level of test.)
      1. Peer to Peer, Client-Server, Domain Model, Active Directory integrated
      2. Number of Servers and workstations
      3. Operating System Details
      4. Major Software Applications
      5. Hardware configuration and setup
      6. Interconnectivity and by what means i.e. T1, Satelite, Wide Area Network, Lease Line Dial up etc.
      7. Encryption/ VPN's utilised etc.
      8. Role of the network or system
   5. Obtained signed Authority to Test
      1. CEO
      2. Risk Manager
      3. System Manager
      4. Data Owners
      5. Security Officer
      6. Relevant ISP
   6. Non-Disclosure Agreement
      1. Full i.e. All information in relation to this task cannot be distributed/ used in research, training, marketing etc.
      2. Limited i.e. Certain information can be used in marketing/ training and research scenarios after agreement has been sort from the customer.
      3. None i.e. All information is freely distributable and not under any restrictions whatsoever.
   7. Special Clearances required
      1. Government vetting
      2. CHECK Team qualified
      3. Mastercard certified
   8. Known waivers/exemptions
      1. Known to Risk Manager
      2. Risk Assessments completed
      3. Exemptions from test
         1. Development builds
         2. Joint-owned equipment
         3. Laptops
         4. Trial Applications
         5. Unstable Hosts
         6. Supplied Network infrastructure for the test only
   9. Contractural constraints
      1. Are there any Service Level Agreement in place that may affect the scope of the test
      2. Waiver letter required for test from contractural partners (this document is required in conjunction with Authority to test above.)
   10. Local equipment requirement
       1. CAT5 taps and speed
       2. Fibre taps/converter requirement
       3. Local Internet access
          1. Filtered
          2. Unfiltered
          3. Downloads/exports allowed
       4. Office space
       5. Power available
       6. Refreshments
   11. Local manpower requirement
       1. Application administrators
       2. Database administrators
       3. Network administrators
       4. Operating System administrators
   12. Points of Contact
       1. Risk Manager
       2. Database Administrator
       3. Local Security Officer
       4. System Administrator
       5. Networking Administrator
       6. ISP
       7. Note: - All should be named and have appropriate 24/7 contact numbers provided.
   13. Reporting Timescales
       1. During Test
          1. Normal
             1. Daily Brief
             2. Interim Brief
             3. End of Test verbal debrief
          2. Exceptional
             1. Upon identifiying Critical vulnerabilities/ exploits
             2. Upon identifying previous Intrusion
             3. Upon finding child pornography/ other activities legally bound to report.
       2. Post Testing
          1. Normal timescale
          2. Local requested timescale
          3. Privacy/Commercial Protective Marking required
          4. Distribution List
   14. Access to Previous tests & reports
       1. Compliance Test
          1. Reason for test
          2. Who carried out
          3. When carried out and if any rectification work was completed.
          4. Release timescale
             1. Start of test - This is important for a Compliance test as previous failings can immediately be re-tested and verified as secured or still vulnerable to exploit etc.
             2. During test
             3. End of test
       2. Vulnerability Assessments
          1. Reason for test
          2. Who carried out
          3. When carried out and if any rectification work was completed.
          4. Release timescale
             1. Start of test
             2. During test
             3. End of test
             4. This can be important during a vulnerability assessment as it can be used as a guide of how the network has progressed during the time of the last test to the current period. Release of this by the customer may not be in there best interests as it is best to have an independant team to assess all vulnerabilties. The customer can then also assess the overall performance of the testing team and thus its value for money in conducting the test.
       3. Penetration Tests
          1. Reason for test
          2. Who carried out
          3. When carried out and if any rectification work was completed.
          4. Release timescale
             1. Start of test
             2. During test
             3. End of test
             4. Appropriate comment to be made in final report reference receipt of these documents and at what point during the test. This provides mitigation points as the information gained is privileged and was used to gain an unfair advantage in potentially accessing the network. Obviously if the documents were made available after the test, the less weight would be stressed in the final report as they would only be used for reference. This can severly disadvantage the customer as they are potentially disclosing exploitable holes within their network infrastructure. An opposite point of view is the fact that the testing team will verify any fixes that have taken place or that the exploitable hole still exists and still needs attention to mitigate or close. From the customer perspective if an exploitable hole is not discovered it can give an indication that the exploit could possibly be risk assessed and managed.
   15. Physical inspection
       1. Major work areas where the majority of users would utilise the equipment.
       2. Network equipment room where all routing infrastructure is housed and secured.
       3. Server room if different from the Network equipment room.
       4. Testing teams planned area of work.