isgc 2017 security workshop
play

ISGC 2017 Security Workshop Sven Gabriel Security Incident - PowerPoint PPT Presentation

ISGC 2017 Security Workshop Sven Gabriel Security Incident handling in Federated Clouds www.egi.eu EGI-Engage is co-funded by the Horizon 2020 Framework Programme of the European Union under grant number 654142 Introduction CSIRT 2017 March


  1. ISGC 2017 Security Workshop Sven Gabriel Security Incident handling in Federated Clouds www.egi.eu EGI-Engage is co-funded by the Horizon 2020 Framework Programme of the European Union under grant number 654142

  2. Introduction CSIRT 2017 March 5 2

  3. Introduction Security in Distributed Infrastructures Incident Prevention Incident/Intrusion Detection Incident Response (IR) IR Communications Containment Forensics CSIRT 2017 March 5 3

  4. Security in Distributed Infrastructures CSIRT 2017 March 5 4

  5. Security and Business Models Why bother about Security, another business model Cyberbunker: Mind Your Own Business policy CSIRT 2017 March 5 5

  6. Security in Distributed Infrastructures Why bother about Security Security always has in impact how users experience services. How much you want to care about security is dependent on your business model. This has a serious impact and is a management decision, see for example: http://www.nytimes.com/2016/09/29/technology/yahoo-data-breach-hacking.html?_r=1 CSIRT 2017 March 5 6

  7. Security and Users/Customers How to sell security to the users/customers Some sociology: https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43265.pdf http://www.nature.com/news/how-to-hack-the-hackers-the-human-side-of-cybercrime-1.19872 CSIRT 2017 March 5 7

  8. Security and Users/Customers Examples from our Infra • Request to patch, . . . • You use our service from an unknown location, . . . • no, we can’t give you root on the compute cluster • no, we will not install your preferred editor on our supercomputer CSIRT 2017 March 5 8

  9. Goal: keep Users/Customers happy Ingredients • Have a clear set of agreed policies (ex. AUP) • Be transparent on why certain actions are requested (Advisories) • Use the proper ’language’ for the intended recipient (Admin/User) • Be prepared to deal with frustrated / swamped users. CSIRT 2017 March 5 9

  10. Security Incidents Incidents, finally . . . CSIRT 2017 March 5 10

  11. Security Incidents in Distributed Infrastructures Definition 1 : A security incident is the act of violating an explicit or implied security policy (ex: local security policy, EGI Acceptable Use Policy) ( https://documents.egi.eu/public/ShowDocument?docid=47 ) • Who violates policies? • Criminals: Automated Attacks, compromised systems rented out for illegal activities (Botnet, used for ddos, spam, distribute malware etc). • Hacktivism, Creative young people • Insiders, Users CSIRT 2017 March 5 11

  12. How attackers access the infra • External, unauthenticated Most serious, needs to be prevented • External, authenticated Ex: stolen Credentials • Local, authenticated Also: Impersonation Vulnerabilities CSIRT 2017 March 5 12

  13. Security in Distributed Infrastructures • Incident Prevention • Incident/Intrusion Detection (also Tue. 16:00, Fyodor, Watz) • Incident Response (Vincent) CSIRT 2017 March 5 13

  14. Who can Work on Security ... CSIRT 2017 March 5 14

  15. Incident Prevention CSIRT 2017 March 5 15

  16. Infrastructure Housekeeping Vulnerability Handling Process: • Vulnerability Detection (often external sources) • Assessment (SVG/RAT) → Criticality • If Critical, develop: HeadsUp/Advisory, Security Monitoring • All Sites need to take action (patch/mitigate) • Follow up (Ticketing) • Monitor the Infrastructure CSIRT 2017 March 5 16

  17. Infrastructure Housekeeping Why: • Prevent being victim of standard attacks (check your logs, a lot background noise) • Clean-Up of an incident is expensive! • Provide an environment where users are ”protected” from each other. • If the infra is not usable/working (for whatever reason) will result in funding issues. CSIRT 2017 March 5 17

  18. Goal: Reducing Security Incidents Number of incidents using grid technology CSIRT 2017 March 5 18

  19. Goal: Reducing Security Incidents Number of incidents using grid technology 1 CSIRT 2017 March 5 18

  20. Grid/Cloud differences • Admin / User role separated in Grid • Grid Admins are Linux Systems experts • Grid Software is verified against EGI’s current Quality Criteria (UMD) • FedCloud RCs (up to Hypervisor, Network) are managed by Admins • VMs are managed by the Users CSIRT 2017 March 5 19

  21. Some Cloud Security Non System Experts (Users) are admins of their Infrastructure they deploy in the cloud. • To mitigate this risk VM Endorsement Policy was developed. • Distinguish between VM Operators/Users • Provide the users with endorsed secure VMs CSIRT 2017 March 5 20

  22. Incident/Intrusion Detection CSIRT 2017 March 5 21

  23. Incident/Intrusion Detection Tue 16:00 Identifying Suspicious Network Activities in Grid Network Tue 16:30 Modern Monitoring Systems (Watz) CSIRT 2017 March 5 22

  24. Incident Response (IR) CSIRT 2017 March 5 23

  25. IR Requirements • Know your perimeter: Security Policies https://wiki.egi.eu/wiki/Security_Policy_Group • Know your Infrastructure, who has which role, what are the communication endpoints. • Have an Incident Response Procedure ( https://wiki.egi.eu/wiki/SEC01 ) CSIRT 2017 March 5 24

  26. Actors and Roles • Site Security Contact • EGI-CSIRT Security Officer on Duty • User • VO-Security Contact • External party CSIRT 2017 March 5 25

  27. IR Communications CSIRT 2017 March 5 26

  28. IR Communications Questions: • You know now the actors, where do you get the contacts? CSIRT 2017 March 5 27

  29. IR Communications Questions: • You know now the actors, where do you get the contacts? • You know that the contacts are in http://goc.egi.eu/ and https://operations-portal.egi.eu/vo/security CSIRT 2017 March 5 27

  30. IR Communications Questions: • You know now the actors, where do you get the contacts? • You know that the contacts are in http://goc.egi.eu/ and https://operations-portal.egi.eu/vo/security • So, . . . what will you ask? . . . report? CSIRT 2017 March 5 27

  31. IR Communications Questions: • You know now the actors, where do you get the contacts? • You know that the contacts are in http://goc.egi.eu/ and https://operations-portal.egi.eu/vo/security • So, . . . what will you ask? . . . report? • , see https://wiki.egi.eu/wiki/EGI_CSIRT: Incident_reporting • Or CSIRT 2017 March 5 27

  32. IR Communications Questions: • You know now the actors, where do you get the contacts? • You know that the contacts are in http://goc.egi.eu/ and https://operations-portal.egi.eu/vo/security • So, . . . what will you ask? . . . report? • , see https://wiki.egi.eu/wiki/EGI_CSIRT: Incident_reporting • Or just contact abuse .at. egi.eu CSIRT 2017 March 5 27

  33. Containment CSIRT 2017 March 5 28

  34. Containment • Stop the incident! How? CSIRT 2017 March 5 29

  35. Containment • Stop the incident! How? • Stop a DN submitting new jobs/starting VMs CSIRT 2017 March 5 29

  36. Containment • Stop the incident! How? • Stop a DN submitting new jobs/starting VMs • Central Argus system CSIRT 2017 March 5 29

  37. Containment • Stop the incident! How? • Stop a DN submitting new jobs/starting VMs • Central Argus system • For the forensics see Vincents talk CSIRT 2017 March 5 29

  38. Forensics CSIRT 2017 March 5 30

  39. Forensics Talk: Computer Forensics Analysis (FyodorVincent) • What went wrong • How to detect it • How to react to it . . . CSIRT 2017 March 5 31

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend