php-deluxe.net - description Penetration test

Penetration test

A penetration test is a method of evaluating the security of a computer system or network by simulating an attack by a malicious hacker. The process involves an active analysis of the system for any weaknesses, technical flaws or vulnerabilities. This analysis is carried out from the position of a potential attacker, and can involve active exploitation of security vulnerabilities. Any security issues that are found will be presented to the system owner together with an assessment of their impact and often with a proposal for mitigation or a technical solution.

== Black box vs. white box ==

Penetration tests can be conducted in several ways. The most common difference is the amount of knowledge of the implementation details of the system being tested that are available to the testers. Black box testing assumes no prior knowledge of the infrastructure to be tested, and the testers must first determine the location and extent of the systems before commencing their analysis. At the other end of the spectrum, white box testing provides the testers with complete knowledge of the infrastructure to be tested, often including network diagrams, source code and IP addressing information. There are also several variations in between, often known as gray box testing.

The relative merits of these approaches are debatable. It is argued that black box testing most closely simulates the actions of a real Cracker_(computing), however this ignores the fact that any targeted attack on a system most probably requires some knowledge of the system, and any insider attacker would be in possession of as much information as the system owners. In most cases it is preferable to assume a worst-case scenario and provide the testers with as much information as they require, assuming that any determined attacker would already have acquired this.

In practice, the services offered by penetration testing firms range from a simple scan of an organisation s IP address space for open ports and identification banners to a full audit of source code for an application.

== Rationale ==

A penetration test should be carried out on any computer system that is to be deployed in a hostile environment, in particular any Internet facing site, before it is deployed. This provides a level of practical assurance that any script kiddie or other more determined attacker will not be able to penetrate the system.

== Methodology ==

access controls, security processes, and physical locations such as buildings, perimeters, and military bases.

The OSSTMM focuses on the technical details of exactly which items need to be tested, what to do before, during, and after a security test, and how to measure the results. OSSTMM is also known for its [Rules of Engagement] which define for both the tester and the client how the test needs to properly run starting from denying false advertising from testers to how the client can expect to receive the report. New tests for international best practices, laws, regulations, and ethical concerns are regularly added and updated.

The National Institute of Standards and Technology (NIST) discusses penetration testing in Special Publication 800-42, Guideline on Network Security Testing. NIST s methodology is less comprehensive than the OSSTMM however it is more likely to be accepted by regulatory agencies. For this reason NIST refers to the OSSTMM.

There is a new Methodology known as the Information Systems Security Assessment Framework (ISSAF) by [http://www.oissg.org Open Information System Security Group]

The Information System Security Assessment Framework (ISSAF) is a peer reviewed structured framework that categorizes information system security assessment into various domains & details specific evaluation or testing criteria for each of these domains. It aims to provide field inputs on security assessment that reflect real life scenarios. ISSAF should primarily be used to fulfill an organization s security assessment requirements and may additionally be used as a reference for meeting other information security needs. ISSAF includes the crucial facet of security processes and, their assessment and hardening to get a complete picture of the vulnerabilities that might exist. The ISSAF however is still in its infancy.

== Standards ==

If you are hiring a company to provide penetration testing services for you, it is important to be able to judge their abilities before engaging them. The process of carrying out a penetration test can reveal sensitive information and organisations must be certain they are dealing with professionals. It is for this reason that most security firms are at pains to show that they do not employ ex-Hackers and that all employees adhere to a strict ethical code. In addition, there are several professional and government certifications that indicate the firms trustworthiness and conformance to industry best practice.

For example, ISECOM produces and hosts the OSSTMM methodology (see above) and will provide training and certification in its use. In 2005, the University of Glamorgan accredited the [http://www.7safe.com/PGC-Postgraduate_Certificate.html Postgraduate Certificate in Penetration Testing & Information Security] , the first of its kind in the world, which includes the [http://www.7safe.com/CSTA-Certified_Security_Testing_Associate.html CSTA] & [http://www.7safe.com/CSTP-Certified_Security_Testing_Professional.html CSTP] certifications. In the UK, CESG (the Communications-Electronics Security Group) has traditionally provided IT health check services for HMG and the public sector. It now maintains an accreditation for its IT Health Check Service, or CHECK. Companies belonging to CHECK must have employees that are security cleared and have passed the CESG Hacking Assault Course called the CESG IT Health CHECK Service.