3.6.2 - Penetration testing
Penetration testing examines whether a system's defences can be bypassed. Learn its purpose and compare an authorised test that simulates an insider with one that simulates an external attacker.
Testing whether resources can be accessed
A security control may look correct in its settings but still leave a route to protected resources.
Penetration testing
Authorised testing that attempts to gain access to protected resources without using the normal means of access, in order to find security weaknesses.
For example, a company may hire a tester to check whether confidential files can be reached by bypassing the expected login or permission controls. The tester is trying to demonstrate a weakness before a malicious attacker exploits it. Finding a flaw is useful evidence even if the system has never had a reported attack.
A legitimate test has the owner's permission and an agreed scope. The scope identifies which systems and actions are permitted. The tester records findings so the owner can repair weaknesses, for example correcting excessive permissions or applying a patch. A later test can check whether the repair works. Permission distinguishes an authorised test from unauthorised access; calling an intrusion “research” does not grant permission.
Worked outcome. A tester finds that a supposedly private document can be retrieved without its expected credentials. The report should identify the exposed resource and the failed control. The organisation restricts access and retests. Installing unrelated software without fixing the exposure would not address the evidence.
Simulating insiders and external attackers
Different starting information lets testers examine different attacker situations.
Continue this lesson.
You’re previewing NovaLearn without an account. Create a free account to read the rest.
Create free account