2.4 - Assessment Types

 2.4 - Assessment types 

 

Key Terms 

    • Payment Card Industry Data Security Standards (PCI-DSS) - The security standards organisations that hold card information must abide by. 
    • Health Insurance Portability and Accountability Act (HIPAA) - The security standards that keep health related information private from the public. 
    • ISO/IEC 27001 – A set of processes and requirements for an organisation’s information security management systems. 
    • Sarbanes Oxley Act (SOX) - Federal regulations that attempt to increase transparency in corporate governance and financial reporting. 
    • Digital Millennium Copyright Act (DMCA) - Federal regulations designed to protect copyrighted works. 
    • Federal Information Security Management Act (FISMA) - Federal regulations that define how government data, operations, and assets are handled. 

 

Purpose of a Penetration Test 

    • Goal-based testing – This test focuses on the end results. The goals are specific but the methods of achieving them are determined by the ethical hackers. A penetration tester should use a wide range of techniques to achieve those goals. Goals should be defined within the compliance of S.M.A.R.T targets. Goals should be realistic and relevant to the test. 
    • Objective-based testing – This test focuses on the overall security of the organisation. The scope of work defines the depth of the test and which objectives the ethical hacker must work towards. If there is a specific part of the organisation, they are worried about, the hacker will be specifically thorough with that part of the examination. 
    • Compliance-based testing – This test is solely to analyse if a company is in compliance with the laws and regulations in that country. This includes the PCI-DSS, HIPAA, ISO/IEC 27001, SOX, DMCA, and FISMA. These regulations do have some limitations. For example, they are often based on outdated password policies and are updated irregularly. The regulations are sometimes also too detailed which can limit security management options. 

 

Merging 

When companies decide to merge or in a company takeover, there must be a combination of systems, policies and regulations. This can often result in a penetration test being needed. In most cases, the company will need to check compatibility between networking systems, physical security, data security, and company culture. These tests identify differences in the 2 companies which, if left unattended, could lead to vulnerabilities. During the test, things could also be revealed that can cause merges or takeovers to fail which may just save a company in the long term. 

 

Supply Chain 

This is when one company needs to transfer materials to another. By creating a supply chain, a business must consider if there are correct connections between the 2 companies, how effective their security is and, if there are any regulations they need to abide by. 

 

Security Teams 

    • Blue teams focus on defensive security. They are responsible for implementing policies and addressing vulnerabilities. 
    • Red teams work against the blue team to test the security of an organisation and find vulnerabilities. The red teams consist of ethical hackers. 
    • Purple teams are pipelines between blue and red teams. However, the purple team can also be offensive and defensive at times. 

Comments

Popular posts from this blog

OSA Assignment 1 - Task 3 GUIDE

OSA Assignment 1 - Task 1 GUIDE

OSA Summer 2023 Mock - Task 1, Assignment 1