Free Newsletter
Register for our Free Newsletters
Newsletter
Zones
Access Control
LeftNav
Alarms
LeftNav
Biometrics
LeftNav
Detection
LeftNav
Deutsche Zone (German Zone)
LeftNav
Education, Training and Professional Services
LeftNav
Government Programmes
LeftNav
Guarding, Equipment and Enforcement
LeftNav
Industrial Computing Security
LeftNav
IT Security
LeftNav
Physical Security
LeftNav
Surveillance
LeftNav
View All
Other Carouselweb publications
Carousel Web
Defense File
New Materials
Pro Health Zone
Pro Manufacturing Zone
Pro Security Zone
Web Lec
 
ProSecurityZone Sponsor
 
ProSecurityZone Sponsor
 
ProSecurityZone Sponsor
 
ProSecurityZone Sponsor
 
ProSecurityZone Sponsor
 
ProSecurityZone Sponsor
 
 
News

IT security penetration testing

Vega Group : 03 November, 2008  (Technical Article)
Paul Newman of VEGA Group offers some insight into how effective penetration testing can be used to understand the vulnerabilities in corporate networks and prevent data leakage
"Lost data official to be charged"… "MI6 photos 'sold on auction site'"… "Discs loss 'entirely avoidable'"… "Fresh benefit data lapse admitted"… "Firm 'broke rules' over data loss"… "More firms 'admit disc failings'"… It seems that rarely a month goes past without the all too familiar headlines, such as those above, dominating our media channels. Public perception around information security (and the processes by which government and suppliers handle or share data) has never been so low.

In response to these security lapses, the UK Government released its final report on Data Handling Procedures in Government on 25 June 2008. One of key recommendations was the introduction of 'new rules on the use of protective measures, such as encryption and penetration testing of systems'.
The UK penetration testing market has grown greatly in recent years, with a number of organisations in the industry offering a wide range of services differing widely in terms of the benefits, cost and quality of the service. But just how far can penetration testing help reduce failings in information security?

This article offers some thoughts on what considerations should be taken to ensure organisations take a comprehensive and responsible approach to penetration testing.

There are many factors that influence the requirement for the penetration testing of a service or facility, and many variables contribute to the outcome of a test. It is first important to obtain a balanced view of the risk, value and justification of the penetration testing process; the requirement for testing may be as a result of a code of connection requirement (CoCo) or as a result of an independent risk assessment.

Another important consideration is that the results of penetration testing are aimed toward providing an independent, unbiased view of the security stance and posture of the systems being tested; the outcome, therefore, should be an objective and useful input into the security procedures.
The testing process should not be seen as either obstructive or attempting to identify security shortfalls in order to lay blame or fault on the teams responsible for designing, building or maintaining the systems in question. An open and informative test will require the assistance and co-operation of many people beyond those actually involved in the commissioning of the penetration test.

A properly executed penetration test provides customers with evidence of any vulnerabilities and the extent to which it may be possible to gain access too or disclose information assets from the boundary of the system. They also provide a baseline for remedial action in order to enhance the information protection strategy.

One of the initial steps to be considered during the scoping requirements phase is to determine the rules of engagement and the operating method to be used by the penetration testing team, in order to satisfy the technical requirement and business objectives of the test. A penetration test can be part of a full security assessment but is often performed as an independent function.

The mechanics of the penetration testing process involves an active analysis of the system for any potential vulnerabilities that may result from improper system configuration, known hardware or software flaws, or from operational weaknesses in process or technical operation. Any security issues that are found during a penetration test should be documented together with an assessment of the impact and a recommendation for either a technical solution or risk mitigation.

A penetration test simulates a hostile attack against a customer's systems in order to identify specific vulnerabilities and to expose methods that may be implemented to gain access to a system. Any identified vulnerabilities discovered and abused by a malicious individual, whether they are an internal or external threat, could pose a risk to the integrity of the system.

Experienced security consultants who are tasked with completing penetration tests attempt to gain access to information assets and resources by leveraging any vulnerabilities in systems from either an internal or external perspective, depending on the requirements of the tests and the operating environment.

In order to provide a level of assurance to the customer that the penetration test has been performed effectively, the following guidelines should be considered to form the baseline for a comprehensive security assessment. The penetration test should be conducted thoroughly and include all necessary channels. It is important that the posture of the test complies with any applicable government regulation and policy, and the results should be measurable against the scoped requirements. The report should contain results that are consistent and repeatable, and the results should only contain facts derived from the testing process.

It should always be appreciated that there is an element of risk associated with the penetration testing activity, especially to systems tested in a live environment. Although this risk is mitigated by the use of experienced professional penetration testers, it can never be fully eliminated.

There are many types of penetration testing covering areas such as networks, communication services and applications. The fundamental processes involved in a penetration test can be broken down as scanning, vulnerability identification, attempted exploitation and reporting. The degree to which these processes are performed, is dependent on the scoping and requirements of the individual test, along with the time assigned to the testing process and reporting phases.

The tools and techniques used when performing a penetration test are dependent on the type of test required and the timescales associated with performing the test. Using a mix of automated assessment tools for vulnerability scanning and mapping, in combination with hands-on manual testing, a knowledge-focussed methodology provides customers with a best-of-breed testing service that will identify risks and issues obtained from potentially non-obvious vectors and attack paths.

An initial penetration test is essential to establishing an unbiased view of an organisation's security stance. However, performing regular penetration testing is an integral factor in ensuring that a system is maintained at a high level of security in line with corporate requirements. Regular testing provides the management team with a constant view of the security of their systems and provides the technical team with tailored advice to assist in improving the effectiveness of the overall security and protection of the systems under their control.

Regular penetration testing should account for new trends in attack techniques and tools. An unbiased penetration test can assist customers in focusing their security resources where they are needed most.
Bookmark and Share
 
Home I Editor's Blog I News by Zone I News by Date I News by Category I Special Reports I Directory I Events I Advertise I Submit Your News I About Us I Guides
 
   © 2012 ProSecurityZone.com
Netgains Logo