Download
1 / 48
650 likes | 806 Views
Ethical Hacking: Overview. Presented By Team Neptune { Eric, Amy, Aung, Sophia, Venus Mae}. Ethical Hacking Principles Managing Incidents Exploring Security Policies Creating Security Policies SANS Web Application Security Policy. Topic Overview. Ethical Hacking Principles.
E N D
Ethical Hacking: Overview Presented By Team Neptune {Eric, Amy, Aung, Sophia, Venus Mae}
Ethical Hacking Principles • Managing Incidents • Exploring Security Policies • Creating Security Policies • SANS Web Application Security Policy Topic Overview
Ethical Hacking Principles Three Different Subcultures:
Ethical Hacking Principles Black Hat Hackers • Use their Skills Unethically • Objective: • To Cause Harm • Financial Gain • Political/Social Agenda • Can be backed by Organized Crime or Nation States
Ethical Hacking Principles Gray Hat Hackers • Access without permission • Malice not intended • Curious to test skills • Can potentially report vulnerabilities
Ethical Hacking Principles White Hat Hackers • Supported by their Targets • Internal or Contracted Employees • Use their Skills Ethically • Look for Exploits/Vulnerabilities • Report known issues • Fix issues within in their scope
Managing Incidents: Incidents vs. Disaster • There is a difference between incident and disaster. • Incidents: • Unplanned • Disrupts day-to-day activities • Disasters: • Large scale • Weeks or months of recovery • Incidents WILL become a disaster if left unchecked
Managing Incidents • There shouldn’t be a delay in response so the issue doesn’t affect other areas. • BEGIN once incident has been reported. • The management incident continues until normal activity has resumed.
Managing Incidents • React ASAP otherwise there could be greater costs to fix a widespread problem.
Managing Incidents • Each company can set up their own set of procedures to handle incidents. • These guidelines can be fine-tuned to meet the needs of companies.
Managing Incidents: Reporting • Train users to identify and log incidents. • Entries need to be made when incidents are reported (Help Desk Ticket) • Unique ID • Who reported the incident? • Description • Date & time • Priority • Location • Category and/or subcategory
Managing Incidents • When responding, make a call or physically go to the site of the problem!
Managing Incidents: Possible Causes • Once possible causes are identified, the priority of the incident gets modified (higher or lower). • Either it gets resolved quickly or it needs to be handed off to a technician with more experience to help solve the issue.
Managing Incidents: Developing and Implementing a Solution • Minor incidents are quick to fix • Major solutions take longer to implement • Run baseline before any changes • Save device and wiring closet configurations • Rerun baseline tests to verify solutions
Managing Incidents: Resolution and Documentation • Communicate areas where the company can help prevent the issue from recurring, whether it be to the customers or employees! • Process: • Close the incident • Get feedback • Include all pertinent facts • Suggest preventative actions
Managing Incidents: What Makes a Strong Team? • They remain calm • Roles are assigned clearly • There is communication between the team and the customers
Managing Incidents • Important keynote! • Management of incidents are reactive. • Steps should be done to approach incidents proactively.
Managing Incidents: Best Practices Lastly, these are important to remember! • Maintain security policies. • Install security patches and virus updates. • Maintain access control lists. • Perform security assessments. • Analyze captured data.
Exploring Security Policies: Creating Security Plan • A Multidisciplinary approach • Defines what security controls are required • Outlines responsibilities • Reassessed on a regular basis (every 3 years)
Exploring Security Policies: Guidelines • Rules of proper conduct are defined. • Clear systems boundaries are demarcated. • There are clear consequences for policy violations.
Exploring Security Policies: Classification • The level of sensitivity is assessed. • The security team identifies individuals and their level of access according to the principle of least privilege. • They are developed internally or by following a template.
SANS Web Application Security Policy Targeted Quick Full OWASP Testing Guide OWASP Top Ten Vulnerabilities 1 2 3
SANS Web Application Security Policy Change Control Process
Sources • SANS Web Application Security Policy https://www.sans.org/security-resources/policies/application-security/pdf/web-application-security-policy • Managing Incidents https://www.lynda.com/Linux-tutorials/Managing-incidents/455716/488923-4.html • Exploring Security Policies https://www.lynda.com/Linux-tutorials/Exploring-security-policies/455716/488924-4.html • Creating Security Policies https://www.lynda.com/Linux-tutorials/Creating-security-policies/455716/488925-4.html • Ethical Hacking Principles https://www.lynda.com/Linux-tutorials/Ethical-hacking-principles/455716/488921-4.html
