Share
Embed
Transcript
35 slides
-
YURY NIÑO ROA Site Reliability Engineer Cloud Infrastructure Engineer Chaos
Engineering Advocate @yurynino https://www.yurynino.dev/ -
• Attacker Motivations • Attacker Profiles • Methods to Prevent
• Considerations • Security and Reliability • Security Chaos Engineering Agenda We are going to talk about www.yurynino.dev -
www.yurynino.dev In 1989 written by Clifford Stoll wrote how to
hunt for a computer hacker who broke into a computer at the Lawrence Berkeley National Laboratory (LBNL). Elliot Alderson, a cybersecurity engineer and hacker with social anxiety disorder and clinical depression. Elliot is recruited by an insurrectionary anarchist known as "Mr. Robot" to join a group of hacktivists called "fsociety". -
Understanding a system’s adversaries is critical for building resilience and
survivability for a wide variety of catastrophes. Adversaries in the security context are human; their actions are calculated to affect the target system in an undesirable way. -
Hobbyists • While debugging programs they discovered flaws that the
original system designers hadn’t noticed. • Curious technologists. They hack for fun! • Motivated by their thirst for knowledge. www.yurynino.dev -
Researchers • Use their security expertise professionally. • Employees, freelancers
working finding vulnerabilities. • Participate in Vulnerability Reward Programs Bug bounties. • Motivated to make systems better, allies to organizations. • Red Teams and penetration testers. www.yurynino.dev -
Governments • Security experts hired by Government organizations. • Everybody
could be a target of a Government. ACTIVITIES Intelligence gathering Military Purposes Policy Domestic www.yurynino.dev -
Activists • They are usually want to take credit publicity.
• Consider whether your business or project is involved in controversial topics. www.yurynino.dev -
Criminal Actors • Commonly they want to commit identities fraud,
steal money and blackmail. • The only barriers to entry for most criminal actors are a bit of time, a computer, and a little cash. www.yurynino.dev -
Artificial Intelligence • Some attacks could be executed without humans.
• Scientists and ethicists are designing machines might be capable enough to learn how to attack each other. • Developers need to consider resilient system design. www.yurynino.dev -
You may not realize you’re a target. Sophistication is not
a true predictor of success. Attackers aren’t always afraid of being caught. Don’t underestimate your adversary. Attribution is hard. Considerations www.yurynino.dev -
Chaos Engineering It is the discipline of experimenting failures in
production in order to reveal their weakness and to build confidence in their resilience capability. https://principlesofchaos.org/ -
Security Chaos Engineering It is the identification of security control
failures through proactive experimentation to build confidence in the system’s ability to defend against malicious conditions in production. Chaos Engineering Book. 2020 -
Principles Hypothesize about Steady State Run Experiments Vary Real-World Events
Automate Experiments www.yurynino.dev -
www.yurynino.dev Hypothesis: After the owner of Root account in Google
Cloud left the company, we could use our cloud in a normal way. Result: Hypothesis disproved. In this experiment the access to Google Cloud is connected to the Active Directory. When an employee left the company his account is dropped and we lost the access to the cloud. Side Effect: Thinking in this scenario allows to consider another applications connected to Active Directory. -
www.yurynino.dev • Introduce latency on security controls. • Drop a
folder like a script would do in production. • Software secret clear text disclosure. • Permission collision in a shared IAM role policy. • Disable service event logging. • Unencrypted Google Cloud Bucket. • Disable MFA. More Examples -
www.yurynino.dev GameDays are interactive team-based learning exercises designed to give
players a chance to put their skills to the test in a real-world, gamified, risk-free environment. A Chaos GameDay is a practice event, and although it can take a whole day, it usually requires only a few hours. The goal of a GameDay is to practice how you, your team, and your supporting systems deal with real-world turbulent conditions. Chaos Gamedays -
www.yurynino.dev Framework Before After During • Pick a hypothesis. •
Pick a style. • Decide who. • Decide where. • Decide when. • Document. • Get approval! • Detect the situation. • Take a deep breath. • Communicate. • Visit dashboards. • Analyze data. • Propose solutions. • Apply and solve! • Write a postmortem. • What Happened • Impact • Duration • Resolution Time • Resolution • Timeline • Action Items -
www.yurynino.dev Framework Before After During • Pick a hypothesis. •
Pick a style. • Decide who. • Decide where. • Decide when. • Document. • Get approval! • Detect the situation. • Take a deep breath. • Communicate. • Visit dashboards. • Analyze data. • Propose solutions. • Apply and solve! • Write a postmortem. • What Happened • Impact • Duration • Resolution Time • Resolution • Timeline • Action Items Evolve • Improve vulnerability DB. • Refine the process. • Adjust metrics. • Validate CMM position. • Adapt next Gameday. • Continuous Verification. -
• The adoption of SCE faces challenges: human factors to
Security issues. • Reducing potential damage and blast radius is critical in Security. • Communication and observability: successful Chaos Security GameDays. • Requirements may collision with experimentation in Security. • You don’t need to be a security expert to start with Security Chaos Engineering. Security Chaos Journey www.yurynino.dev