Ic Sconf2010presentation Dp Bh


Published on

My presentation on how to handle a data breach at the 2nd Annuual Data Protection Conference run by the Irish Computer Society

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The three certainties with regards to information securityDeath and TaxesYou will have an incident.How you respond to an incident will have a direct influence on the impact that incident may have to your costs, reputation and ability to conduct business.
  • Traditional focus on PreventionPoliciesFirewallsAnti-Virus SoftwareIntrusion Detection SystemsIf turned on !!Little Attention Paid to RespondingResponse Focus Primarily onVirusesMinor Policy Breaches
  • More solutions do not necessarily guarantee you are secure.Neither does more standards such as ISO 27001 or PCI DSS. Yes they will make your security more efficient and better, but you still will at some stage suffer a breach.
  • Traditional ResponseAdhocUnplannedDeal with it as it happensResults inProlonged incidentsIf You Know You Have Been AttackedLack of metrics and measurementsBad Guys & Gals getting awayInappropriate Response Can Result;Disclosure of confidential information.Prolonged recovery times.Lack of evidence for a criminal or civil case.Negative impact to the organisation’s image.Potential legal and/or compliance Issues.Potential Legal Cases from Third Party Organisations.Exposure to Legal/Libel Cases From Employees/Individuals.IT Manager Updating Their CV
  • IT Manager Updating Their CVInvariably IT get blamed for either letting the incident happen in the first place or for not responding appropriately
  • Structured and Formalised Response provides;Positive Security PostureIncidents Dealt with Quickly, Efficiently and EffectivelyRapid and Accurate Assessment of IncidentsChoosing Most Appropriate Response.Shortened Recovery Times.Minimised Business Disruption.Confidence to Proceed with a Court Case.Regulatory and Legal Compliance.Potential Reduction in Incidents.Accurate Reporting and Metrics
  • Do you want this man sitting across from you as a result of an incident?
  • Talk about the publicly known breaches
  • Websites compromised to host phishing sites and malwareCompromised SSH accountsDDOS attacksPrivacy breach on website’s databaseConficker
  • ComposedInformation SecurityOperationsHuman ResourcesLegalPublic RelationsFacilities ManagementUnder Control of Information Security
  • Log filesNetwork DevicesPeopleNot just via the support deskBaseliningWhat is the norm for your network?ExternalVulernability ListsPartnersThird Parties
  • Forensics SoftwareCommercial vs. Open SourceIncident Tracking & RecordingDigital SignaturesSpare MediaBackupsEvidence bagsEvidence formsPhysical EvidenceCCTV, Swipe Card accessNetwork Sniffers Centralised Time SourceTraining CoursesNotebooksDigital CameraOut of Band CommunicationsEmail may be compromisedSupport System may be compromisedWar RoomSecure StorageCoffee!!
  • How are Incidents Reported?Incident ClassificationProcedures in Place for Expected IncidentsProcedures in Place for Unexpected IncidentsWho declares an Incident?Who to involve and when?Team available 24x7?Escalation TreeTypical ProceduresMalware/Computer Virus infectionExternal Unauthorised Access to SystemsInternal Unauthorised Access to SystemsTheft of Computer Equipment and Related Data.Discovery of Illegal Content on Company’s ResourcesSerious Breach of the AUPMinor Breach of the AUPWebsite Defacement.Denial of Service Attack.Email Flood Attack.Third Party Compromise.Disclosure of Confidential Information.
  • Incidents Can Occur 24x7What takes Priority?Mitigate the impact of IncidentGather as Much Evidence As PossibleRestore SystemsWhat Authority has IRT teamE.g. Take systems offlineIntegrate with Business ContinuityCan IRT invoke Business Continuity Plan?Integrate With Other ProcessesChange Control etc.Security vs Service !!
  • Some Skills not available In-houseLegalForensicsPublic RelationsAgree Terms & Conditions before an IncidentSuppliersISPs, Telecomms, HostingPartnersCustomersAn Garda SiochanaGarda Computer Crime UnitPart of Garda Bureau of Fraud InvestigationHow do you Report a Computer Crime?Contact Local Garda StationRefer to Garda Computer Crime UnitWhen Should You Contact Garda Computer Crime UnitToday !!Do the above before you have an incident as it is not something you want to negotiate in the middle of responding to an incident or breach.
  • Run Practise Drills.Identify Weaknesses in IR.Review Effectiveness of Incident Response.Ensure Everyone Aware of Roles & Responsibilities.Regularly Test Network for Vulnerabilities.Regularly Normalise Network & Systems.Test Staff Awareness.Test Management Awareness.Can you contact everyone when you need to?For example will the network engineer in their twenties who is single be available to respond at 10 p.m. on a Friday night? How about the manager who has to do the school run in the morning?
  • Establish a formal Incident Response Process.Take into account your business environmentRegulatory and legal obligationsPolicy on incident response
  • Most important thing to do is not to panic.Panic causes stress and stress in turn can lead to bad decisions.Incorrect decisions or inappropriate responses can have severe impact on the outcome of your response.
  • Contrary to what your reactions might be saying you should Stop and Access the situation.Fire chief when arriving at the scene of an incident always asks “What is going on?”Unmanaged response can result in corrupted logs, lack of forensic evidence or alerting the unauthorized user.- Ask what is happening?- How was the incident reported?- What systems are impacted?- What approach does mgmt want to take – investigate & prosecute or get systems up and running?- What regulatory or legal obligations do you have? Have you got the appropriate skills on board?Do you need external expertise?
  • Containment involves limiting the scope and impact of the information security incident.Stopping the spread of a virusPreventing compromise of other machinesUse tools such as- Segregating the networkUsing ACL on routers to block or filter trafficUnplugging network cablesShutting down systemsRemember your servers contain your crown jewels, sometimes we need to sacrifice the village to defend the castle.
  • Eradicating an incident entails identifying and removing the root causeSimply restoring a system to operational status without identifying the root cause may result in incident re-occurring again at a later stage.To ensure the root cause has been identified and eradicated, and to also support any future criminal or civil court cases, the following shall be followed;- All relevant evidence be gathered in a forensically sound manner by trained personnel using approved software and equipment.All steps and actions should be clearly documented All copied of original media and log files being investigated should be digitally signed and stored securely to prevent tampering. - All investigations should be conducted on verified copies of the original media and log files.
  • Recovery means restoring a system(s) back to their normal operational status.This may requirerestoring system(s) from backupsreinstalling from known and certified original media.Repairing infected files using AV softwareApplying patches to the systemPart of the recovery process shall ensure that the integrity of the backup being used for the restore operation has been thoroughly verified and that the restore operation was successful.
  • Once recovered systems should be monitored to ensure they are not compromised again.It is possible that your investigation may not have discovered an alternative route into your system that the criminals could use again.It is also possible that the root cause has been identified incorrectly and that the attack happened through a different means not addressed in the recovery process.You could also have missed a compromised system in your investigation and this could be used to compromise you again.Monitor the system(s) carefully for any unusual behavior and investigate further
  • Throughout the information security incident it is essential that appropriate communications are maintained. During an information security incident it is also essential that confidentiality is maintained throughout the incident’s lifecycle as the issue could result in a court case or disciplinary measures against a staff member.Communication media could be compromised e.g. email so alternatives will need to be used.Other things to considerPress enquiriesAn Garda SiochanaData Protection ComissionerRegulatory bodiesThird Parties such as clients or business partnersPublicStaffManagementLegal
  • To disclose or not to disclose?You may have no optionIssue may be known publicly – website defacement etc.You may be obliged to report, morally, regulatory or contractuallyIs it better that you manage the details of the issue or a third party like the press?
  • Ic Sconf2010presentation Dp Bh

    1. 1. Data Breach !!What Next?<br />2ndAnnual ICS Data Protection Conference<br />
    2. 2. Infosec Professional Certainties<br />
    3. 3. Typical IT Security<br />3<br />
    4. 4. But …<br />
    5. 5. Controls Will be Bypassed<br />
    6. 6. Traditional Incident Response<br />
    7. 7. IT Manager In Line Of Fire<br />
    8. 8. Why Improve Incident Response?<br />Fail to Prepare – Prepare to Fail<br />
    9. 9. Why Improve Incident Response?<br />
    10. 10. So Far in 2010<br />
    11. 11. Increasing Number of Irish Incidents<br />WWW.IRISS.IE<br />Membership is Free<br />
    12. 12. Establish Team<br />
    13. 13. Set up Alerting Mechanisms<br />
    14. 14. Identify Tools<br />
    15. 15. Standard Operating Procedures<br />
    16. 16. Agree Authority of IRT<br />
    17. 17. Establish External Relationships<br />
    18. 18. Practise Makes Perfect<br />
    19. 19. Response Process<br />
    20. 20. Don’t<br />
    21. 21. Do Nothing !!<br />
    22. 22. Contain the Incident<br />
    23. 23. Eradicate the Root Cause<br />
    24. 24. Recover Systems<br />
    25. 25. Monitor<br />
    26. 26. Communicate Regularly<br />
    27. 27. Disclosure?<br />
    28. 28. More information<br />CSIRT Handbook<br />http://www.cert.org/archive/pdf/csirt-handbook.pdf<br />Forming an Incident Response Team<br />http://www.auscert.org.au/render.html?it=2252<br />Incident Response White Paper – BH Consulting<br />http://www.bhconsulting.ie/Incident%20Response%20White%20Paper.pdf<br />RFC2350: Expectations for Computer Security Incident Response<br />http://www.rfc-archive.org/getrfc.php?rfc=2350<br />Organisational Models for Computer Security Incident Response Teams<br />http://www.cert.org/archive/pdf/03hb001.pdf<br />The SANS Institute’s Reading Room<br />http://www.sans.org/reading_room<br />
    29. 29. More Resources<br />Guidelines for Evidence Collection and Archiving (RFC 3227)<br />http://www.ietf.org/rfc/rfc3227.txt<br />Resources for Computer Security IncidentResponse Teams (CSIRTs)<br />http://www.cert.org/csirts/resources.html<br />RFC 2196: Site Security Handbook<br />http://www.faqs.org/rfcs/rfc2196.html <br />ENISA Step by Step Guide for setting up CERTS<br />http://enisa.europa.eu/doc/pdf/deliverables/enisa_csirt_setting_up_guide.pdf<br />CSIRT Case Classification (Example for enterprise CSIRT)<br />http://www.first.org/resources/guides/csirt_case_classification.html<br />
    30. 30. Questions?<br />Brian.honan@bhconsulting.ie<br />www.bhconsulting.ie<br />www.twitter.com/brianhonan<br />www.bhconsulting.ie/securitywatch<br />Tel : +353 – 1 - 4404065<br />
    31. 31. Thank you<br />