Metrics for High-Level Gap Analysis in Security Programs

1. Metrics

2. SABSA High-Level Framework

3. Gap Analysis The difference between where you are and where you want to be: • # malware infections/month • Rate of finding illegal software, hardware • Security awareness training averages

4. SEI/COBIT Level 4 Monitoring:Includes Metrics • Metrics inform management (and independent auditors) of the effectiveness of the security program • Monitoring achievement of control objective may be more important than perfecting security procedures

5. Which metrics to use? Business-Driven Technology-Driven Addresses recent threats observed by CERT CERT: Computer Emergency Readiness Team Addresses recent forensic data Addresses specific business risks • Inherent industry risks • Tailored to organization • Measures adherence to control objectives

6. Monitoring Function: Business-Driven Metrics Executive mgmt is interested in risk, budget, policy. Review every 6 months-1 year Technical details: E.g., firewall, logs, IPS, vulnerability tests. Review weekly. Automate statistics. Determine effectiveness of security program: risk changes, compliance, incident response tests. Review quarterly to half-year

7. Monitoring Function: Business-Driven Metrics Project Plan or Budget Metrics Risk performance Disaster Recovery Test results Audit results Regulatory compliance results Vulnerability Scan results Server config. standards compliance IDS monitoring results Firewall log analysis Patch mgmt status Policy compliance metrics Exceptions to policy/standards Changes in process or system affecting risk Incident management effectiveness

8. Which metrics? Step 1:What are the most important security areas … threats …. regulation … to monitor in your organization? Step 2: Which metrics make the most sense to collect. Can they be automated? Step 3: Consider the 3 perspectives: strategic, tactical, operational metrics, relative to 3 audiences.

9. Monitoring Function: Metrics

10. Monitoring Function: Metrics

11. Workbook: MetricsMetrics Selected What are the most important areas to monitor in your organization? Cracking Attempt Lunatic gunman Major Risks: FERPA Violation Web Availability

12. SANS-Recommended Critical Controls for Effective Cyber Defense Technology-Driven Metrics

13. Creating a baseline configuration of network

14. Noticing inappropriate ‘additions’ to the network New PC New AP New wireless

15. Checking the security configuration of network Patched? Legal software? Firewall on & security configured? Antivirus on and patched? Limit USB access? WPA2 AES, EAP/ TLS? Monitor Network? Withstands attacks? SQL, buffer overflow, cross-site scripting, clickjacking, …

16. Noticing inappropriate actions New sys admin or user acct Transfer of confidential data or illegal packets Detect new network service

17. SANS: Critical Controls for Effective Cyber Defense Metric: Temporarily install unauthorized software/hardware on a device. It should be: found within 24 hours (or 2 minutes?) isolated within one hour confirmed by alert/email reported every 24 hours until device is removed.

18. SANS Critical Control 1:Inventory of Authorized Devices Ensure all devices (with IP address) on network are known, configured properly, and patched. Scan network daily or use DHCP reports or passive monitoring. Compare results with baseline configuration. Metric: Temporarily install unauthorized device.

19. SANS: Critical Control 2:Inventory of Authorized Software Ensure all software is approved and recently patched • Whitelist defines the permitted list of software. • Blacklist defines illegal software (e.g., IT tools). • Endpoint Security Suites (ESS) contain antivirus, antispyware, firewall, IDS/IPS, s/w white/blacklisting. • Metric: Temporarily install unauthorized software on a device.

20. SANS Critical Control 3:Secure Configurations for Hardware & Software All devices are hardened using recommended security configurations Illegal software list exists, includes Telnet, VNC, RDP New software is quarantined and monitored. Imaged software is maintained in an updated state. Build secure images, and use configuration checking tools daily. Metric: Temporarily attempt to change a set of random configurations.

21. SANS Critical Control 4:Continuous Vulnerability Assessment Run vulnerability scans on all systems at least weekly, preferably daily. Problem fixes are verified through additional scans. • Vulnerability scanning tools (updated) for: wireless, server, endpoint, etc. • Automated patch management tools notify via email when all systems have been patched. • Metric: If the scan does not complete in 24 hours, an email notification occurs.

22. SANS Critical Control 5:Malware Defense Antivirus/antispyware is always updated • Run against all data • shared files, server data, mobile data. • Additional controls: blocking social media, limiting external devices (USB), using web proxy gateways, network monitoring. • Endpoint security suites can report tool is updated and active on all systems • Metric: For benign malware (e.g., security/hacking tool) install, antivirus prevents installation or execution or quarantines software • sends an alert/email within one hour indicating specific device and owner

23. SANS Critical Control 6:Application S/W Security New application software is tested for security vulnerabilities: • Web vulnerabilities: buffer overflow, SQL injection, cross-site scripting, cross-site request forgery, clickjacking of code, and performance during DDOS attacks. • S/W validates input for size, type • S/W does not report system error messages directly • Automated testing includes static code analyzers and automated web scanning. • Configurations include application firewalls and hardened databases. • Metric: An attack on the software generates a log/email within 24 hours (or less). • Automated web scanning occurs weekly or daily

24. SANS Critical Control 7:Wireless Device Control Wireless access points are securely configured with WPA2 protocol and AES encryption. Extensible Authentication Protocol-Transport Layer Security (EAP/TLS) provides mutual authentication. Only registered, security-approved devices are able to connect Wireless networks are configured for the minimum required radio footprint. Metrics: Wireless intrusion detection systems detect available wireless access points and deactivate rogue access points within 1 hour Vulnerability scanners can detect unauthorized wireless access points connected to the Internet.

25. SANS Critical Control 8:Data Recovery Capability Backups are maintained at least weekly and more often for critical data. Backups are encrypted and securely stored. Multiple staff can perform backup/recovery. Metric: Test backups quarterly for a random sample of systems. This includes operating system, software, and data restoration.

26. SANS Critical Control 9:Security Skills Assessment Security awareness training is required for end users, system owners. Security training is necessary for programmers, system, security and network administrators. • Metric: Test security awareness understanding • Periodically test social engineering tests via phishing emails and phone call • Employees who fail a test must attend a class

27. SANS Critical Control 10:Secure Network Configurations A configuration db tracks approved configurations in config. mgmt. for network devices: firewalls, routers, switches. Two-factor identification is used for network devices. Tools: Tools perform rule set sanity checking for Access Control Lists. Metric: Any change to the configuration of a network device is reported within 24 hours

28. SANS Critical Controls 11. Control of Network Ports, Protocols, and Services: • Default Deny packets. • Periodically review for restriction • Measure time to recognize added network service 12. Controlled Administrative Privilege: • Minimal elevated privileges • Passwords are complex, changed periodically, 2-factor • Measure time to recognize new sys admin

29. SANS Critical Controls 13. Boundary Defense: • Use firewall zones to filter incoming and outgoing traffic. • Blacklist & whitelist network addresses • Measure time to recognize unauthorized packets 14. Analysis of Security Audit Logs: • Server logs are write-only and archived for months. • Firewalls log all allowed and blocked traffic. • Unauthorized access attempts are logged • Measure time to recognize no log space

30. SANS Critical Controls 15. Need to Know Access: Prevent exfiltration of data to competitors. • Data classification • Restrictive firewall configurations • Logged access to confidential data • Measure time to recognize unauthorized access 16. Account Monitoring and Control: Terminated accounts -> removed Expired password/ disabled/ locked out accounts, -> investigated Failed logins -> lockouts; Inactivity -> locked sessions Unusual time access -> alert. Data exfiltration recognized by keywords. Measure time to recognize new/ changed user accounts

31. SANS Critical Controls 17. Data Loss Prevention: • Prevent exfiltration of proprietary or confidential info. • Encryption of mobile and USB devices; • Disable USB • Measure time to recognize transfer of confidential data file 18. Incident Response: • Incident Response Plan defines who does what for various conditions. • IRP includes contact information for third party contractors.

32. SANS Critical Controls 19. Secure Network Engineering: • Separate zones: DMZ, middleware, private network • DMZ accessed through proxy firewall • DMZ DNS is in DMZ; internal DNS is in internal zone, … • Emergency config. for restricted network is ready for quick deployment. 20. Penetration Tests: • Penetration tests = vulnerability tests + attacker tests. • Red Team exercises test incident response team reactions. • Measure false positive, false negative, true positive rate

33. Question The difference between where an organization performs and where they intend to perform is known as: • Gap analysis • Quality Control • Performance Measurement • Benchmarking

34. Question The MOST important metrics when measuring compliance include: • Metrics most easily automated • Metrics related to intrusion detection • Those recommended by best practices • Metrics measuring conformance to policy

35. Reference