340 likes | 497 Views
Vulnerability Testing Approach. Prepared By: Phil Cheese Nov 2008. Outline . Structure of Technology UK Security Team Why we test What we test When we test How we test Demo of a unix platform test Hot topics Questions and Answers. Vulnerability Test Team. UK Tech. Security Mgr.
E N D
Vulnerability Testing Approach Prepared By: Phil Cheese Nov 2008
Outline • Structure of Technology UK Security Team • Why we test • What we test • When we test • How we test • Demo of a unix platform test • Hot topics • Questions and Answers
Vulnerability Test Team UK Tech. Security Mgr Security Operations Group CISO Security Consultants UK Technology Security teams Review New Systems Vulnerability Testing Security Monitoring Mail, Logs, IDS, Firewall
Definition Penetration testing v Vulnerability testing ? • Wikepedia “Security testing techniques scour for vulnerabilities or security holes in applications. These vulnerabilities leave applications open to exploitation. Ideally, security testing is implemented throughout the entire software development life cycle (SDLC) so that vulnerabilities may be addressed in a timely and thorough manner. Unfortunately, testing is often conducted as anafterthought at the end of the development cycle.” Why ? – test against standards, identify misconfigurations, old vunerable versions of software, test drive • Ethics & Legality
Preventing financial loss through fraud (hackers, extortionists and disgruntled employees) or through lost revenue due to unreliable business systems and processes. Proving due diligence and compliance to your industry regulators, customers and shareholders. Non-compliance can result in your organisation losing business, receiving heavy fines, gathering bad PR or ultimately failing. Protecting your brand by avoiding loss of consumer confidence and business reputation. vulnerability testing helps shape information security strategy through identifying vulnerabilities and quantifying their impact and likelihood so that they can be managed proactively; budget can be allocated and corrective measures implemented. Why testing
Defining the scope • Full-Scale vs. Targeted Testing • Platform, Network, Database, Applications • Remote vs. Local Testing • In-house v outsourcing
Defense in depth Network
Nmap Nessus Tester www.vodafone.co.uk Network elements e.g SGSN’s, HLR’s Sun Solaris Application Server Redhat Apache Web server HP-UX Oracle DB Windows File server
Assuria Agents Tester www.vodafone.co.uk Network elements e.g SGSN’s, HLR’s Sun Solaris Application Server Redhat Apache Web server HP-UX Oracle DB Windows File server
NGS Squirrel Tester www.vodafone.co.uk Network elements e.g SGSN’s, HLR’s Sun Solaris Application Server Redhat Apache Web server HP-UX Oracle DB Windows File server
Appscan, Superwalk Tester www.vodafone.co.uk Network elements e.g SGSN’s, HLR’s Sun Solaris Application Server Redhat Apache Web server HP-UX Oracle DB Windows File server
Tester www.vodafone.co.uk Network elements e.g SGSN’s, HLR’s Sun Solaris Application Server Redhat Apache Web server HP-UX Oracle DB Windows File server AssuriaCLI Remote test (Data Centre)
Remote platform vulnerability assessment using Assuria Auditor & workbench via the command line • “It is better to voyage hopefully than to drive to Oldham” • FTP and install scripts • Run scans • Copy off raw results files • Generate csv files • Import results into workbench • Review scan results • Producing reports • Agreeing remedial actions and re-testing
Vulnerability testing - hot topics • PCI-DSS – keeping Security vendor industry going! https://www.pcisecuritystandards.org/ • Appliances and automation – keep your auditors happy http://www.qualys.com/products/qg_suite/ http://www.ncircle.com/index.php?s=products • Virtualisation and middleware vulnerabilities – don’t forget’em…. http://labs.mwrinfosecurity.com/ • Exploitation tools – Metasploit framework, Canvas, Core Impact. BEEF http://www.metasploit.com/ http://www.immunitysec.com/ http://www.coresecurity.com/ http://www.bindshell.net/tools/beef
Conclusions • In depth, holistic approach to security testing • Testing needs to take place during the development lifecycle • Can be complex and time consuming • Outsource specialist testing to third party vendors • Commercial tools easy to maintain and use but can be expensive • “A fool with a tool is still a fool” • Results from tools need analysis and put into a ‘business risk’ context