ProCheckUp - Penetration Testing, Frequently Asked Questions (FAQs)

Friday 9 May 2008

		Why is ProCheckNet more detailed than manual penetration testing?

		The use of AI allows for more complex decision making and ensures that a higher number of iterations of attack are performed on the target environment whilst also ensuring higher quality and consistency.

		What methodology does ProCheckNet follow?

		The award-winning ProCheckNet technology combines the methodology of a manual penetration testing team with the functionality of an automated attack system to create the most comprehensive penetration testing service available. Click here to see how it works

		Is the testing and reporting entirely automated?

		No. ProCheckUp security consultants analyse and verify the raw data to ensure that the test has been thorough and comprehensive. Depending upon the environment, consultants may conduct additional manual tests. They will then interpret the results to produce a tailored, business-focused report.

		Can ProCheckUp be used to test third party systems?

		Yes. ProCheckUp are frequently contracted to test the IT infrastructure of clients business partners and systems that are hosted or managed by third parties.

		Is there a flexible way I can test my systems on an ad-hoc basis?

		Yes. ProCheckUp offer a flexible solution whereby customers can call off testing on any number of targets at any time. Click here to request further information.

		Can ProCheckNet reports satisfy regulatory requirements?

		Yes. ProCheckUp reports are used by financial organisations and FTSE 100 companies to satisfy FSA and auditors requirements and are approved to perform security assessment services under the MasterCard Site Data Protection Program. Click here to download FSA information Click here for more information on MasterCard SDP Compliance

		What guidelines do ProCheckUp follow for penetration testing?

		ProCheckUp exceed OWASP guidelines for penetration testing and are MasterCard SDP Compliant. Download a copy of 'The Ten Most Critical Web Application Security Vulnerabilities' (2004) here or visit www.owasp.org for more information.


	Site Map
	Privacy Policy

	Terms and Conditions