Clone of . For those who would prefer to not be tracked by MS.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

656 lines
101 KiB

5 years ago
3 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
3 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
3 years ago
3 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
3 years ago
3 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
3 years ago
2 years ago
2 years ago
3 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
3 years ago
3 years ago
2 years ago
5 years ago
4 years ago
3 years ago
2 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
2 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
2 years ago
4 years ago
3 years ago
2 years ago
2 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
3 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
2 years ago
2 years ago
3 years ago
2 years ago
2 years ago
3 years ago
  1. # Basic Security Principles/Information
  2. ## Table of Contents
  3. - [Basics](#basics)
  4. - [Principles](#principles)
  5. - [Advice](#advice)
  6. - [Classes/Types of Vulnerabilities](#classes)
  7. - [How to Suck at InfoSec](#suck)
  8. - [Getting Started with InfoSec](#getstart)
  9. - [Background](#background)
  10. - [Being the First Security Person/Starting a Security Program/Growing it](#fps)
  11. - [Briefing and Reporting](#briefing)
  12. - [Scaling a Security Program](#scalingsec)
  13. - [Building a Security Team](#buildteam)
  14. - [Cognitive Bias](#cbias)
  15. - [Mental Models](#mm)
  16. - [Comedy](#comedy)
  17. - [Command Lines & OS Basics](#cli)
  18. - [Critical Thinking](#critthink)
  19. - [Common Vulnerability Scoring System(CVSS)](#cvss)
  20. - [Data Breaches](#breaches)
  21. - [Fundamental Papers](#fund)
  22. - [General Good Stuff](#ggs)
  23. - [Helping Others](#helpo)
  24. - [History](#history)
  25. - [How to Ask Better Questions](#bq)
  26. - [Information Processing](#ip)
  27. - [Learning](#learning)
  28. - [Metrics](#metrics)
  29. - [Networking](#networking)
  30. - [Normalization of Deviance](#nom)
  31. - [Problem Solving](#ps)
  32. - [Project Management](#pms)
  33. - [Ransomware](#ransomware)
  34. - [Regular Expressions](#regex)
  35. - [Research](#research)
  36. - [Request for Service/Product](#rfsp)
  37. - [Risk](#risk)
  38. - [Securing yourself](#secself)
  39. - [Software Testing](#softwaretesting)
  40. - [Statistics](#statistics)
  41. - [System Design](#systemdesign)
  42. - [TableTop Exercises](#ttx)
  43. - [Task Automation](#automation)
  44. - [Tools to Know About](#ttka)
  45. - [Vendor Security](#vensec)
  46. - [The Web](#web)
  47. - [Zero Trust](#zerotrust)
  48. - [Fun](#fun)
  49. - [Breach](#breach)
  50. -------------------------
  51. ## Contents
  52. * **Basics** <a name="basics"></a>
  53. * **101**
  54. * [Primum non nocere - Wikipedia](
  55. * Primum non nocere (Classical Latin: [ˈpriːmũː noːn nɔˈkeːrɛ]) is a Latin phrase that means "first, do no harm."
  56. * The ""I don't know what I'm doing but I want to learn 'security'" portion:
  57. * Security imo is a field like philosophy. On its own, it has limited application in the immediate. However, when applied to other subjects, its value/usefulness becomes more apparent.
  58. * You can learn security as a discipline, or you can learn general basic concepts and then apply that to a line of code/function/program/Architecture/Design/etc.
  59. * There isn't a single path to take, and not all paths go straight forward, you may go down one path only to find you end up reading about the basics for something you considered ignorable/not worth your time, because in a new perspective, you've seen the 'hidden' value.
  60. * The "I wanna be a hacker!" advice:
  61. 1. Learn basic security concepts
  62. * check out the Security+ syllabus by Comptia for ideas.
  63. * [Computer Science Distilled: Learn the Art of Solving Computational Problems - Wladston Ferreira Filho](, Plus plenty of reading on Wikipedia: [Computer Science - Wikipedia](
  64. 2. Learn x86(-64) or ARM ASM. - I recommend [Programming from the Ground Up](, [Azeria's series on writing ARM ASM](, and the [Intel® 64 and IA-32 Architectures Software Developer Manuals](
  65. 3. Learn C. Read [The C Programming Language(K&R)](, but learn C elsewhere.
  66. 4. Congratulations! You now have the skills and abilities(at least the basics) to start doing your own research and identifiying where you want to further develop your skills.
  67. 5. Further reading I could recommend:
  68. * Linux([Understanding the Linux Kernel - Daniel P. Bovet, Marco Cesati](
  69. * macOS([MacOS and `*`OS Internals - Jonathan Levin](
  70. * Windows([Windows Internals Book series]( & [Windows Via C/C++](
  71. * Also this list: [Information security / Hacking for noobs](
  72. * Also [Why Cyber Security is Hard to Learn (Tips For Success!)](
  73. * **Intros**
  74. * [Alice and Bob - Wikipedia](
  75. * [Security Engineering (3rd ed) - Ross Anderson](
  76. * [10 Immutable Laws of Security Administration - Scott Culp(](
  77. * [Learning the Ropes 101: Introduction -](
  78. * [InfoSec Newbie List by Mubix](
  79. * [infosec_getting_started](
  80. * A collection of resources/documentation/links/etc to help people learn about Infosec and break into the field.
  81. * [Brandolini's Law - Wikipedia](
  82. * Brandolini's law, also known as the bullshit asymmetry principle, is an internet adage which emphasizes the difficulty of debunking bullshit: "The amount of energy needed to refute bullshit is an order of magnitude bigger than to produce it."
  83. * [Maslow’s Hierarchy of Security Controls - Lee Holmes(2014)](
  84. * [How to Secure Anything - Veeral Patel](
  85. * How to systematically secure anything: a repository about security engineering
  86. * [Signalling (economics) - Wikipedia](
  87. * **Basic Security Concepts**
  88. * [Information security - Wikipedia](
  89. * [Confused deputy problem - Wikipedia](
  90. * [Principle of least privilege - Wikipedia](
  91. * [Object-capability model - Wikipedia](
  92. * [Capability-based security - Wikipedia](
  93. * **Computer Science**
  94. * [40 Key Computer Science Concepts Explained In Layman’s Terms -](
  95. * [Software Engineering Body of Knowledge (SWEBOK) - IEEE](
  96. * [Infra Living Standard —](
  97. * Last Updated 30 August 2019; The Infra Standard aims to define the fundamental concepts upon which standards are built.
  98. * **Mentality**
  99. * [One week of bugs -](
  100. * [I could do that in a weekend! -](
  101. * [Zero-One-Infinity Rule -](
  102. * [Improving Infosec (or any Community/Industry) in One Simple but Mindful Step - Matt Graeber](
  103. * [Tacit Knowledge](
  104. * Tacit knowledge or implicit knowledge (as opposed to formal, codified or explicit knowledge) is the kind of knowledge that is difficult to transfer to another person by means of writing it down or verbalizing it. For example, that London is in the United Kingdom is a piece of explicit knowledge that can be written down, transmitted, and understood by a recipient. However, the ability to speak a language, ride a bicycle, knead dough, play a musical instrument, or design and use complex equipment requires all sorts of knowledge which is not always known explicitly, even by expert practitioners, and which is difficult or impossible to explicitly transfer to other people.
  105. * **Things**
  106. * [Every TED Talk Ever, In One Brutal Parody - FastCompany](
  107. * [The Most Important Productivity Lesson I Ever Learned - Daniel Messler](
  108. * [How to exit Vim](
  109. * **Videos**
  110. * [Foundations of Computer Security - Mason Egger(2020)](
  111. * This is the first talk in a series of Tech Talks from DigitalOcean around Computer Security titled Foundations of Computer Security. This talk will walk you through the fundamentals of computer security, from its history, to common threats you may face, to recommended practices to keep you safe.
  112. * [Every Security Team is a Software Team Now - Dino Dai Zovi(Black Hat USA 2019 Keynote)](
  113. * As software is eating the world, every company is becoming a software company. This doesn’t mean that every company is shipping software products, it means that services and products in every field are becoming increasingly driven, powered, and differentiated by software. Let’s explore what that will do to how cybersecurity is practiced in enterprises of all types. Peter Drucker famously said that “Culture eats strategy for breakfast.” There have been two large cultural shifts in software engineering over the last 20 years that created the successful strategies behind how software is eating the world. First, there was Agile (2001). In response to the inefficiencies of classic “waterfall” software development, Agile focused on breaking down the barriers between software requirements, development, and testing by having software development teams own their roadmaps as well as their quality. Separate product management organizations evolved into product owners working directly with the software team. Similarly, separate quality assurance organizations evolved into a focus on building quality into the software development process. This should remind us of how we talk about needing to build security in, but most importantly, this change was effected by software teams themselves vs. forced onto them by a separate security organization. There is a lesson to be learned there. Next came DevOps (2009), which brought the agile mindset to server operations. Software teams now began to own their deployment and their uptime. Treating software teams as the end-user and customer has driven the replacement of traditional ops with the cloud and replacing the traditional stack with serverless models. Ops teams evolved into software teams that provide platforms, tools, and self-service infrastructure to internal teams. They provide value by increasing internal teams’ productivity while reducing costs to the entire organization through economies of scale and other efficiencies. When a cross-functional team owns their features, their quality, their deployment, and their uptime, they fully own their end-to-end value stream. Next, they will evolve to also own their own risks and fully own their end-to-end impact. There are two big shifts involved as teams begin to own their end-to-end impact: software teams need to own their own security now and security teams need to become full-stack software teams. Just as separate product management and quality assurance organizations diffused into cross-functional software teams, security must now do the same. At his re:Invent 2018 Keynote, Amazon’s CTO Werner Vogels proclaimed that “security is everyone’s job now, not just the security team’s.” But if security is every teams’ job, what is the security team’s job? Just like how classic ops teams became internal infrastructure software teams, security teams will become internal security software teams that deliver value to internal teams through self-service platforms and tools. Security teams that adopt this approach will reduce the risk to the organization the most while also minimizing impact to overall productivity. In this talk, we’ll explore how this is already being done across high-performing companies and how to foster this security transformation at yours.
  114. * [Real Software Engineering - Glenn Vanderburg(Software Art Thou)](
  115. * The idea is spreading that perhaps software development is simply incompatible with engineering; that software developers are not, and never will be, real engineers. Glenn Vanderburg, VP of Engineering at First, takes a fresh look at what that really should mean for this field. With an extra 45 years of experience about the task of programming, and a broad survey of the varied different engineering disciplines, can we envision a future for a field of “software engineering” that is worthy of the name?
  116. * [Real Software Engineering by Glenn Vanderburg(Lone Star Ruby Conference(2010)](
  117. * Software engineering as it's taught in universities simply doesn't work. It doesn't produce software systems of high quality, and it doesn't produce them for low cost. Sometimes, even when practiced rigorously, it doesn't produce systems at all. That's odd, because in every other field, the term "engineering" is reserved for methods that work. What then, does real software engineering look like? How can we consistently deliver high-quality systems to our customers and employers in a timely fashion and for a reasonable cost? In this session, we'll discuss where software engineering went wrong, and build the case that disciplined Agile methods, far from being "anti-engineering" (as they are often described), actually represent the best of engineering principles applied to the task of software development.
  118. * [Software Security Field Guide for the Bewildered - zwischenzugs](
  119. * **Principles** <a name="principles"></a>
  120. * [Akin's Laws of Spacecraft Design - David L. Akin](
  121. * [Types of Authentication](
  122. * [Access control best practices](
  123. * [Information Theory - Wikipedia](
  124. * [Encoding vs. Encryption vs. Hashing vs. Obfuscation - Daniel Messler](
  125. * [Safety with Dignity Booklist - Sidney Dekker](
  126. * [10 Immutable Laws of Security (Microsoft TechNet) Non-original](
  127. * [Ten Immutable Laws Of Security (Version 2.0) -](
  128. * [You Can’t Do Everything: The Importance of Prioritization in Security - RecordedFuture](
  129. * **Advice** <a name="advice"></a>
  130. * [Every thought about giving and taking advice I’ve ever had, as concisely as possible - Alexey Guzey(2020)](
  131. * **Classes/Types of Vulnerabilities** <a name="classes"></a>
  132. * [MITRE Common Attack Pattern Enumeration and Classification(CAPEC)](
  133. * [Race Condition Exploits - Prabhaker Mateti](
  134. * **How to Suck at InfoSec** <a name="suck"></a>
  135. * [How to Suck at Information Security – A Cheat Sheet](
  136. * [How not to Infosec - Dan Tentler](
  137. * **Getting Started with InfoSec** <a name="getstart"></a>
  138. * [ - mubix](
  139. * List of links on getting started in InfoSec/Starting a career.
  140. * [Breaking Into Information Security A Modern Guide - 0xsha](
  141. * [Passwords in a file - erratasec](
  142. * **Background** <a name="background"></a>
  143. * [The Shoulders of InfoSec - Jack Daniels(BSides Tampa 2018)](
  144. * If I have seen further it is by standing on the shoulders of giants; Most famously attributed to Sir Isaac Newton, this quote reflects the sentiment of this project. All of us in the field of information security stand on the shoulders of giants, this project is dedicated to shining a light on those shoulders- the known and unknown. In this presentation I will tell the stories some foundation figures in our industry and communities, some famous, some infamous, some unknown.
  145. * [Lessons Learned - A 15 year Retrospective - Price McDonald(BSides Indy 2018)](
  146. * Life is full of blessings and pitfalls. This is my attempt to let others learn from my past mistakes and hopefully keep working and pressing on towards their goals.
  147. * **Being the First Security Person/Starting a Security Program/Growing it** <a name="fps"></a>
  148. * **101**
  149. * Asset Inventory
  150. * Baseline Hardening
  151. * Developer Training/Secure Coding Training
  152. * File Integrity Monitoring
  153. * Firewall
  154. * Logging
  155. * Mobile Device Management
  156. * Monitoring
  157. * Patch Management
  158. * Policies
  159. * User Security Awareness Training
  160. * Vendor Management
  161. * Vulnerability Management
  162. * **'Example Template Sample'(not sure where I found this originally)**
  163. * Define Problem(Inlcuding impact)
  164. * Explain solution
  165. * How does it solve the issue
  166. * What resources/people are needed?
  167. * Why will it work?
  168. * Are there alternatives?
  169. * Why did you choose this solution?
  170. * benefits of solution
  171. * Cost of implementation
  172. * Quantifications
  173. * Risk of doing/not doing
  174. * Timeline
  175. * **'General' Security Program**
  176. * **Articles/Blogposts/Writeups**
  177. * [Starting Up Security - Ryan McGeehan](
  178. * A collection of information security essays and links to help growing teams manage risks.
  179. * [A comprehensive guide to security for startups - David Cowan](
  180. * [How Early-Stage Startups Can Enlist The Right Amount of Security As They Grow -](
  181. * [Starting Up Security - Ryan McGeehan](
  182. * [Killing “Chicken Little”: Measure and eliminate risk through forecasting. - Ryan McGeehan](
  183. * [Building an InfoSec Organisation - Week 1 to 6 - Greg van der Gaast(2020)](
  184. * [Security Strategy for Small Medium Business - Claus Houman, Infosystir, Jim Nitterauer, Moose(DEFCON27 Blue Team Village](
  185. * **Talks/Presentations/Videos**
  186. * [Empathy as a Service to Create a Culture of Security - Tracy Z. Maleeff(Derbycon2019)](
  187. * True empathy requires that you step outside your own emotions to view things entirely from the perspective of the other person.? Reject the idea that end users are the weakest security link. Rather, think of them as your front line of defense. Start the foundation of creating a strong culture of security within your organization by treating end users with respect, dignity, and empathy. Security professionals need to utilize soft skills, in addition to technical tools, to empower the end users to prepare them against phishing and other social engineering attacks. Based on a library science technique that has been adapted for Information Security professionals, this talk will illustrate how changing the way you interact with end users can make for a better security atmosphere.
  188. * [Building a Modern Security Engineering Organization - Zane Lackey(Derbycon 2014)](
  189. * Continuous deployment and the DevOps philosophy have forever changed the ways in which businesses operate. This talk with discuss how security adapts effectively to these changes- specifically covering: – Practical advice for building and scaling modern AppSec and NetSec programs – Lessons learned for organizations seeking to launch a bug bounty program – How to run realistic attack simulations and learn the signals of compromise in your environment
  190. * [Startup security: Starting a security program at a startup - Evan Johnson(OWASP AppSecCali 2019)](
  191. * There's no blueprint for how to be successful at a small startup. Startups are quirky, ambiguous, and full of challenges and broken processes. Startups also have a high risk tolerance and rarely introduce security from the beginning. This talk will discuss different approaches to introducing security at a company, how to be successful as a security professional at a startup, and how to integrate your security team with the rest of the company.
  192. * [So You've Inherited a Security Department, Now What? - Amanda Berlin & Lee Brotherston(Derbycon 2016)](
  193. * Over the last decade, technology as a whole has exploded worldwide and corporations have struggled to keep pace. Usability and revenue creation have been the key motivating factors, ignoring the proactive design and security required for long-term stability. With the increase of breaking news hacks, record breaking data leaks, and ransomware attacks it is our job to not only scrape by with default installs but to secure our data and assets to the best of our abilities. There will always be cases where you will walk into an environment that is a metaphorical train wreck. So many of us have been there. We've walked into an environment that has exploded with technology, but no talent to manage it, no leadership to distinguish FUD from real threats, and either zero infosec budget or so much they aren't sure what to do with it. If you or someone you know are currently in this situation, we're here to help. We'll go over great steps to start with that will have little impact on budget, but a large impact on moving forward for a more secure environment. It is important to be able to implement low cost security technology and prioritize threats to show upper level management that due diligence has been done before they throw money at blinky boxes.
  194. * [Twubhubbook: Like an Appsec Program, but for Startups - Brent Johnson, Neil Matatall(OWASP AppSec CA 2017)](
  195. * Simulated walk through of two 'security' contractors being brought on to establish security within a 'startup'. Good talk.
  196. * [Run your security program like a boss / practical governance advice - Justin Leapline & Rockie Brockway(Derbycon 2017)](
  197. * Let’s face it; it’s not easy to run a security governance program. With the continuing pressure of keeping our information secure and breach-free while management doesn’t see the need of increasing budget if there isn’t an incident occurring or compliance need. So how does someone in the trenches measure, monitor, and communicate this to ensure that you get the buy-in needed - or at least get the acceptance from management on the risk. It’s something that everyone in a security leadership position struggles with. Through this talk, we will be discussing some of the key points in implementing, managing, and creating oversight to communicate both internally to the security team and externally with the company. And don’t worry, the points we will be discussing will be applicable across the board - from small businesses to Fortune 100s. Also, we will be releasing some helpful tools in aiding your quest to the nirvana of a simple security governance program. You don't want to miss it!
  198. * [Reaching Across the Isle: Improving Security Through Partnership - Kevin Gennuso(Derbycon 2017)](
  199. * Information security has been a challenge since the dawn of computer networking. Improving the situation requires coordination and cooperation, not an adversarial stance between The Business, Security and IT. The answer isn't more endpoint agents, blinky boxes, or vendor pitches. The answer lies in partnering with all teams with a common purpose: improved security.
  200. * [We Come Bearing Gifts: Enabling Product Security with Culture and Cloud - Astha Singhal, Patrick Thomas(OWASP AppSec Cali2018)](
  201. * This talk explores that counter-intuitive premise, and shows how it is not just possible but *necessary* to discard many traditional security behaviors in order to support modern high-velocity, cloud-centric engineering teams. For the product security team at Netflix, this is the logical implication of a cultural commitment to enabling the organization. Attendees will learn how to replace heavy-handed gating with an automation-first approach, and build powerful security capabilities on top of cloud deployment primitives. Specific examples including provable application identity, immutable and continuous deployment, and secret bootstrapping illustrate how this approach balances security impact with engineering enablement.
  202. * [Building a Modern Security Engineering Organization - Zane Lackey(OWASP AppSec California2015](
  203. * Continuous deployment and the DevOps philosophy have forever changed the ways in which businesses operate. This talk with discuss how security adapts effectively to these changes, specifically covering: Practical advice for building and scaling modern AppSec and NetSec programs; Lessons learned for organizations seeking to launch a bug bounty program; How to run realistic attack simulations and learn the signals of compromise in your environment
  204. * [Where do I start The first 365 days of building a security program - Hudson Bush(ShellCon2018)](
  205. * Scenario: You've been put in charge of InfoSec for a business with no existing security posture and the executive team thinks that Antivirus and Firewall is a sufficient InfoSec budget. They expect results in one year. If you're thinking '`Oh $(*7, I have to do what?'`, this talk is for you. At the end of this talk you will have a roadmap for the first year of implementing a security program, with some understanding of what those who have come before you have done. I hope to explain my mistakes so that you don't have to make mine; you can make your own.
  206. * [starting an AppSec Program: An Honest Retrospective - John Melton](
  207. * This talk will cover the lessons learned from a 2-year journey starting an appsec program at a small-medium sized company that previously had no security program. This will be an honest look at what worked, what didn't work, as well as a follow-up analysis. There will be plenty of stories, common sense perspective, as well as discussion around goal-setting and execution. This will be the talk I wish I had two years ago when I was starting this adventure.
  208. * [Startup security: Starting a security program at a startup - Evan Johnson(AppSecCali 2019)](
  209. * There's no blueprint for how to be successful at a small startup. Startups are quirky, ambiguous, and full of challenges and broken processes. Startups also have a high risk tolerance and rarely introduce security from the beginning. This talk will discuss different approaches to introducing security at a company, how to be successful as a security professional at a startup, and how to integrate your security team with the rest of the company.
  210. * [Scrapping for Pennies: How to implement security without a budget - Ryan Wisniewski(BSides Columbus Ohio2019)](
  211. * This talk focuses on how to implement the CIS Top 20 controls using open source and free tools. Ryan identifies each control objective, the commercial product, and the free product to achieve the control.
  212. * **AppSec Program**
  213. * **Articles/Blogposts/Writeups**
  214. * [OWASP Security Champions Playbook](
  215. * [A bug goes skateboarding on Boehm’s Curve - Ulf Eriksson(2013)](
  216. * [Your 30-60-90 Day AppSec Plan - Hope Goslin(2020)](
  217. * [Thoughts on Starting an Application Security Program - Christopher Emerson](
  218. * [Part 2](
  219. * [One Man Shop: Building an effective security program all by yourself - Tim Mcguffin(Defcon22)](
  220. * **Talks/Presentations/Videos**
  221. * [Pushing left like a boss - Tanya Janca(DevSecCon Singapore2018)](
  222. * With incident response and penetration testing currently receiving most of our application security dollars, it would appear that industry has decided to treat the symptom instead of the disease. “Pushing left” refers to starting security earlier in the SDLC; addressing the problem throughout the process. From scanning your code with a vulnerability scanner to red team exercises, developer education programs and bug bounties, this talk will show you how to ‘push left’, like a boss.
  223. * [Starting Strength for AppSec - Fredrick Lee(OWASP AppSec Cali2019)](
  224. * [Slides](
  225. * [Working with Developers for Fun and Progress - Leif Dreizler(OWASP AppSec Cali2019)](
  226. * Forging a strong relationship with developers is essential part of creating an impactful AppSec program. Without it, your team will have little idea what's going on and will have trouble getting bugs fixed and features shipped. Segment has built strong ties to developers using our competition-based training featuring Burp Suite and OWASP Juice Shop, partnership during implementation of tooling, and contributions to the existing codebase. This presentation is chock full of practical examples and references that attendees can bring back to their organization.
  227. * [Jumpstarting Your Appsec Program - Julia Knecht & Jacob Lords(BSidesSLC 2020)](
  228. * [Empathy for the (Devel)oper: Lessons Learned Building An Application Security Module - Yolonda Smith(NolaCon2019)](
  229. * Security teams spend a lot of time focused on the results and impact of what happens when applications FAIL at security. In turn, we have a bad habit of 'Monday-Morning-Quarterback'ing all the things that should have happened to prevent the security failure in the first place. But have you ever attempted to fully implement ALL of the security advice that's out there in conjunction with business priorities? Well, I did. In this presentation, I will share what I learned about what it takes to get application security right from design to delivery, how to communicate about REAL risk (without the FUD) and why we should eliminate the word 'just' from our remediation recommendations.
  230. * **Product Security Program**
  231. * **Articles/Blogposts/Writeups**
  232. * **Talks/Presentations/Videos**
  233. * [Product Security Shouldn't be Painful - Wim Remes(Derbycon 2019)](
  234. * There is more pressure than ever to produce secure products. In healthcare, IoT, ICS and virtually any segment where connected devices are prevalent, both customer requirements and regulatory pressure force manufacturers to make security of their products a key feature. With this presentation we will share a framework that allows organizations to implement product security practices that do not hamper innovation. With a focus on building a frictionless relationship with developers and engineers, as well as showing progress to the business, we will enable participants to do exactly the same without making the mistakes we did.
  235. * [How to Conduct a Product Security Test: And How it Fits Into the Larger Security Strategy - Dr. Jared DeMott(GrrCON 2018)](
  236. * **Security Awareness/Training Program**
  237. * **Articles/Blogposts/Writeups**
  238. * **Talks/Presentations/Videos**
  239. * [Building An Information Security Awareness Program from Scratch - Bill Gardner and Valerie Thomas(Derbycon 2013)](
  240. * Description:Most organization’s Security Awareness Programs suck: they involved ‘canned’ video presentations or someone is HR explaining computer use policies. Others are extremely expensive and beyond the reach of the budgets of smaller organizations. This talk will show you how to build a Security Awareness Program from scratch for little or no money, and how to engage your users so that they get the most out of the program.
  241. * **DFIR Program**
  242. * [0Day to HeroDay: Bringing a company from scorched earth to a modern security organization - Ryan Wisniewski(ShowMeCon2019)](
  243. * This talk will outline how a company was brought down to its knees from a ransomware attack, how it rose from the ashes, and how it now has a full security organization. Ryan will take you through the thrilling adventure of building incident response, system architecture, disaster recovery, and system operations on the fly while the business was down - and how the group ensured the business could come back online without risk of reinfection. Then, he will discuss how he started a security organization from scratch and talk through the challenges of maturing an organization that was on the brink of destruction just a few months ago.
  244. * **Briefing and Reporting** <a name="briefing"></a>
  245. * See [Docs and Reports](./
  246. * **Scaling a Security Program** <a name="scalingsec"></a>
  247. * **101**
  248. * [How to 10X Your Company’s Security (Without a Series D) - Clint Gibler(BSidesSF2020)](
  249. * [Slides](
  250. * I’ll summarize and distill the insights, unique tips and tricks, and actionable lessons learned from a vast number of DevSecOps/modern AppSec talks and blog posts, saving attendees 100s of hours. I’ll show where we’ve been, where we’re going, and provide a lengthy bibliography for further review.
  251. * **Articles/Blogposts/Writeups**
  252. * [Scaling Appsec at Netflix - Astha Singhal](
  253. * [Building analysts from the ground up - Jack Crook](
  254. * [Scaling security in a high growth company: our journey at Sqreen - Jean-Baptiste Aviat(2020)](
  255. * [How to use frameworks to implement your Security Paved Road - Jean-Baptiste Aviat(2020)](
  256. * **Talks/Presentations/Videos**
  257. * [DevSecOps State of the Union - Clint Gibler(BSidesSF 2019)](
  258. * Many companies have shared their lessons learned in scaling their security efforts, leading to hundreds of blog posts and conference talks. Sharing knowledge is fantastic, but when you're a busy AppSec engineer or manager struggling to keep up with day-to-day requirements, it can be difficult to stay on top of or even be aware of relevant research. This talk will summarize and distill the unique tips and tricks, lessons learned, and tools discussed in a vast number of blog posts and conference talks over the past few years and combine it with knowledge gained from in-person discussions with AppSec engineers at a number of companies with mature security teams. Topics covered will include: Principles, mindsets, and methodologies of highly effective AppSec teams, Best practices in developing security champions and building a positive security culture, High value engineering projects that can prevent classes of bugs, How and where to integrate security automation into the CI/CD process in a high signal, low noise way, Open source tools that help with one or more of the above. Attendees will leave this talk with an understanding of the current state of the art in DevSecOps, links to tools they can use, resources where they can dive into specific topics of interest, and most importantly an actionable path forward for taking their security program to the next level.
  259. * [Efforts in Scaling Application Security Programs - Eric Fay(ShellCon2018)](
  260. * With organizational success comes the exciting period of ever-increasing scale and scope. This talk will cover some of the past and current efforts that Eric personally took on while creating and scaling the application security program at Hulu. A retrospective look will be taken at the focus points, tradeoffs and decisions made by the application security team while keeping up with the growth and continued success of Hulu.
  261. * [Scale your security with DevSecOps: 4 valuable mindsets and principles - Clint Gibler(2019)](
  262. * [A​ Pragmatic Approach for Internal Security Partnerships - Scott Behrens, Esha Kanekar(OWASP AppSecCali 2019)](
  263. * Why do we have such a hard time getting engineering teams to care about vulnerabilities? How is it that we are fixing lots of vulnerabilities, yet are still falling ever further behind on the actual risks? These questions both have the same answer, but getting to it requires empathy, trust, courage, and a giant step back from our day-to-day approach to security. In this talk we will share our experiences about creating proactive partnerships with engineering and product teams. From the ways we have seen this fail to recent success stories, we will illustrate specific practices that help developers and security teams focus and align on a shared view of risk, rather than a laundry list of vulnerabilities: the leverage that comes from enabling rather than gating, automating for visibility and action to manage scale, threat modeling across organizations rather than individual applications, and the particulars of how we get big security features onto busy product teams' roadmaps.
  264. * [Efforts in Scaling Application Security Programs - Eric Fay(ShellCon2018)](
  265. * With organizational success comes the exciting period of ever-increasing scale and scope. This talk will cover some of the past and current efforts that Eric personally took on while creating and scaling the application security program at Hulu. A retrospective look will be taken at the focus points, tradeoffs and decisions made by the application security team while keeping up with the growth and continued success of Hulu.
  266. * [Year[0]: AppSec at a Startup - Leif Dreizler(LASCON2019)](
  267. * Have you wanted to be on the application security team at a startup, but were worried about having an employer that can’t figure out how to monetize its user base, being compensated in potentially worthless stock options, or discovering your company’s business model is based on selling a $400 juicer and expensive juice packets that could actually be squeezed by hand? If so, then this talk is for you! From the safety of the audience you’ll hear about the first year of an appsec program at a tech startup. We’ll cover how to win over the hearts and minds of your developers, useful tooling/automation, and other topics to rapidly improve the security of a growing SaaS startup.
  268. * [(in)Secure Development - Why some product teams are great and others … aren’t... - Koen Hendrix(AppSecCali 2019)](
  269. * In this presentation, Koen will share his experiences with Product Teams at Riot Games and how those teams do or do not take security into consideration. Every product team is unique; but they all behave in similar security patterns, and care about security in predictable ways. Using metrics of our Bug Bounty program and security review process, we’ll dissect the impact that team culture and process have on the security posture of a product. The framework that we’ve created allows you to quickly see what makes a good team good, and how other teams can improve. Taking into account how agile organisations want to operate, we will look at some tools you can introduce into your product teams to help raise the security bar.
  270. * [The Call is Coming From Inside the House: Lessons in Securing Internal Apps - Hongyi Hu(OWASP AppSec Cali 2019)](
  271. * Come hear a dramatic and humorous tale of internal appsec and the technical and management lessons we learned along the way. Even if your focus is on securing external apps, this talk will be relevant for you. You’ll hear about what worked well for us and what didn’t, including: Finding a useful mental model to organize your roadmap; Starting with the basics: authn/z, TLS, etc.; Rolling out Content Security Policy; Using SameSite cookies as a powerful entry point regulation mechanism; Leveraging WAFs for useful detection and response; Using internal apps as a training ground for new security engineers
  272. * [Jumpstarting Your Appsec Program - Julia Knecht & Jacob Lords(BSidesSLC 2020)](
  273. * **Building a Security Team** <a name="buildteam"></a>
  274. * [How to Build a Security Team and Program - Coleen Coolidge(BSidesSF2017)](
  275. * [This is not fine - Surviving Cynicism and Building Happy Security Teams - Chris Deibler(BlueHat v18 2018)](
  276. * **Red Team, Blue Team, Purple Team, Green Team** <a name="team"></a>
  277. * See [RedTeam](./
  278. * [The Difference Between Red, Blue, and Purple Teams - Daniel Miessler](
  279. * [Red Teams - Ryan McGeehan(2015)](
  280. * [Bridging the gaps between Red and Blue teaming - Andy Gill(2020)](
  281. * [Oh My God... Vulnerabiltiy Assessment, Penetration Testing, Redteaming... - Florian Hansemann(2020)](
  282. * [The Four Phases of Offensive Security Teams - mubix(2020)](
  283. * **Purple Teaming**
  284. * [Purple Teaming: The Pen-Test Grows Up - Bryce Galbraith](
  285. * This webcast will cover: Why your annual pen-test is a recipe for disaster, and what you can do about it.; Why many Red and Blue Teams are ineffective despite their efforts, and how to turn this around.; Several real-world TTPs that adversaries utilize (including demos) to completely dominate organizations, shockingly fast.; How to begin to perform adversary emulation and Purple Teaming.; Several helpful tools and resources you can begin to explore immediately...; As Einstein wisely stated, Insanity is doing the same thing over and over again and expecting different results. There is a better way...
  286. * [Purple Team Exposed](
  287. * Are you looking to rapidly improve your security posture or train a new member of your security organization? Are you a Blue Team member looking to cross train with Red Team or vice versa? Purple Teaming could be the answer to your problems. You may have already heard about Purple Teaming through a spare think piece online, casual mentions or even rage tweets, but few know what makes a Purple Team. In this talk I will cover how to build your own Purple Team function from the ground up using applied gap analysis, creating meaningful test cases, modifying tools, cross-training possibilities, and automation frameworks. We'll walk through the methodology together so you leave with the tools and experience you need to do it yourself. If implemented, this can give you a better knowledge of your security baseline, improvements in defenses, opportunities for internal training and mentorship, and an increased dialogue between Red and Blue.
  288. * **Having a Pentest Performed**
  289. * [Red Team Assessment and Penetration Testing - Manga Sridhar Akella](
  290. * [Pen Tests and Red Teams are NOT the same - Carole Theriault](
  291. * [Putting your security assessment budget on a leash while avoiding the Pentest Puppy Mill - John Strand, Paul Asadoorian(2013)](
  292. * The goal of a penetration test should be to elevate your security, not line the pocket of the pentester. In this webcast, Paul and John discuss ways to structure your pentest so that you aren't paying for shells from a Pentest Puppy Mill, but instead paying for reproducible results that will provide a baseline for future testing.
  293. * [What to Expect When You're Expecting a Penetration Test - CJ Cox & Bryan Strand(2020)](
  294. * **Measuring Results of a Red Team/Pentest**
  295. * [Measuring a red team or penetration test. - Ryan McGeehan](
  296. * [A Red Team Maturity Model -](
  297. * **Cognitive Bias** <a name="cbias"></a>
  298. * [List of cognitive biases - Wikipedia](
  299. * [58 cognitive biases that screw up everything we do - Business Insider](
  300. * [Mental Models: The Best Way to Make Intelligent Decisions (109 Models Explained) - Farnam Street](
  301. * [Spotlight effect - Wikipedia](
  302. * [Curse of knowledge - Wikipedia](
  303. * The curse of knowledge is a cognitive bias that occurs when an individual, communicating with other individuals, unknowingly assumes that the others have the background to understand. This bias is also called by some authors the curse of expertise, although that term is also used to refer to various other phenomena.
  304. * [Kuleshov effect](
  305. * The Kuleshov effect is a film editing (montage) effect demonstrated by Soviet filmmaker Lev Kuleshov in the 1910s and 1920s. It is a mental phenomenon by which viewers derive more meaning from the interaction of two sequential shots than from a single shot in isolation.
  306. * [Asch conformity experiments - Wikipedia](
  307. * [Automation bias - Wikipedia](
  308. * Automation bias is the propensity for humans to favor suggestions from automated decision-making systems and to ignore contradictory information made without automation, even if it is correct.
  309. * [Why Do People Neglect Maintenance? - Andy, Jess, Lee(The Maintainers 2019)](
  310. * **Mental Models** <a name="mm"></a>
  311. * [The Map Is Not the Territory - Farnam Street](
  312. * The map of reality is not reality. Even the best maps are imperfect. That’s because they are reductions of what they represent. If a map were to represent the territory with perfect fidelity, it would no longer be a reduction and thus would no longer be useful to us. A map can also be a snapshot of a point in time, representing something that no longer exists. This is important to keep in mind as we think through problems and make better decisions.
  313. * [Coastline paradox - Wikipedia](
  314. * The coastline paradox is the counterintuitive observation that the coastline of a landmass does not have a well-defined length. This results from the fractal curve-like properties of coastlines, i.e., the fact that a coastline typically has a fractal dimension (which in fact makes the notion of length inapplicable).
  315. * [Information Security Mental Models - Chris Sanders](
  316. * [The Mechanics of Modern Thievery (Part 1 of 3) - Greg Johnson(2020)](
  317. * Specifically the metaphor the preface provides. If you look at credentials stored within repositories as similar to keys dropped on the street, it becomes easier to understand how and why passwords & credentials are left in code, beyond 'Developers are lazy/stupid'.
  318. * **Comedy** <a name="comedy"></a>
  319. * [The Website is Down #1: Sales Guy vs. Web Dude](
  320. * [BOFH Index](
  321. * This is a collection of links to most of the BOFH stories from 2000 to 2016 (For BOFH episodes from before 2000, please see the [Official Archive)](
  322. * [Microservices](
  323. * Satire or documentary.
  324. * **Command Lines & OS Basics** <a name="cli"></a>
  325. * **Linux/MacOS**
  326. * **Articles/Resources**
  327. * **System Basics**
  328. * [Everything is a file - Wikipedia](
  329. * [Unix: the Other White Meat - Adam Len Compton & David Boyd(BSides Cleveland 2019)](
  330. * **Bash**
  331. * [Bash Guide for Beginners -](
  332. * The Bash Guide for Beginners gets you started with Bash scripting and bridges the gap between the Bash HOWTO and the Advanced Bash Scripting Guide. Everybody who wants to make life easier on themselves, power users and sysadmins alike, can benefit from reading this practical course. The guide contains lots of examples and exercises at the end of each chapter, demonstrating the theory and helping you practice. Bash is available on a wide variety of UNIX, Linux, MS Windows and other systems.
  333. * [The BashGuide](
  334. * This guide aims to aid people interested in learning to work with BASH. It aspires to teach good practice techniques for using BASH, and writing simple scripts. This guide is targeted at beginning users. It assumes no advanced knowledge -- just the ability to login to a Unix-like system and open a command-line (terminal) interface. It will help if you know how to use a text editor; we will not be covering editors, nor do we endorse any particular editor choice. Familiarity with the fundamental Unix tool set, or with other programming languages or programming concepts, is not required, but those who have such knowledge may understand some of the examples more quickly.
  335. * [Bash Pitfalls -](
  336. * [Concise GNU Bash: An Introduction to Advanced Usage - James Panacciulli @ LinuxFest Northwest 2017](
  337. * [Slides](
  338. * A broad (but not too shallow) introduction to Bash features for users familiar with command line environments who want to go beyond simple command execution. Exciting concepts and syntax illustrated in the slides and demonstrated with live examples. Topics include command types, parameters (arguments, variables, arrays, special parameters), parameter expansion (interpolation, directly or with truncation or substitution), stream redirection, compound commands (loops, groups, conditionals), subshells, brace expansion (word and sequence generation), tests and pattern matching, branching (if, case, logical operators), functions, and the encapsulation of parameters and functions for expansion into distinct Bash instances (run your functions in a root shell or on remote hosts via SSH).
  339. * **`*`grep**
  340. * [learn_gnugrep_ripgrep](
  341. * Example based guide to mastering GNU grep and ripgrep
  342. * [ripgrep is faster than {grep, ag, git grep, ucg, pt, sift} - Andrew Gallant](
  343. * [rga: ripgrep, but also search in PDFs, E-Books, Office documents, zip, tar.gz, etc.](
  344. * rga is a line-oriented search tool that allows you to look for a regex in a multitude of file types. rga wraps the awesome ripgrep and enables it to search in pdf, docx, sqlite, jpg, movie subtitles (mkv, mp4), etc.
  345. * **SSH**
  346. * [Secure Shell - Wikipedia](
  347. * Secure Shell (SSH) is a cryptographic network protocol for operating network services securely over an unsecured network. Typical applications include remote command-line, login, and remote command execution, but any network service can be secured with SSH.
  348. * [OpenSSH](
  349. * [SSH](
  350. * **tmux & screen**
  351. * **tmux**
  352. * [tmux](
  353. * tmux is a terminal multiplexer: it enables a number of terminals to be created, accessed, and controlled from a single screen. tmux may be detached from a screen and continue running in the background, then later reattached.
  354. * [Getting Started - tmux](
  355. * [tmux manpage](
  356. * [A Quick and Easy Guide to tmux - Ham Vocke](
  357. * [tmux plugin manager](
  358. * Installs and loads tmux plugins.
  359. * [Introduction to tmux - ippsec](
  360. * [.tmux - oh my tmux!](
  361. * Self-contained, pretty and versatile .tmux.conf configuration file.
  362. * **Screen**
  363. * [GNU Screen -](
  364. * Screen is a full-screen window manager that multiplexes a physical terminal between several processes, typically interactive shells. Each virtual terminal provides the functions of the DEC VT100 terminal and, in addition, several control functions from the ANSI X3.64 (ISO 6429) and ISO 2022 standards (e.g., insert/delete line and support for multiple character sets). There is a scrollback history buffer for each virtual terminal and a copy-and-paste mechanism that allows the user to move text regions between windows. When screen is called, it creates a single window with a shell in it (or the specified command) and then gets out of your way so that you can use the program as you normally would. Then, at any time, you can create new (full-screen) windows with other programs in them (including more shells), kill the current window, view a list of the active windows, turn output logging on and off, copy text between windows, view the scrollback history, switch between windows, etc. All windows run their programs completely independent of each other. Programs continue to run when their window is currently not visible and even when the whole screen session is detached from the users terminal.
  365. * [Screen User’s Manual -](
  366. * **emacs/vim/nano**
  367. * **emacs**
  368. * **Nano**
  369. * **Vim**
  370. * [Mastering the Vim Language - Chris Toomey](
  371. * [Slides](
  372. * Chris Toomey talks about mastering the Vim language. Vim's core is the amazing command mappings and text objects that allow for countless combinations to define precise edits. Learn how to master the built-in commands, motions, and text objects, and even how to extend the Vim language for even more power!
  373. * [Evil Mode: Or, How I Learned to Stop Worrying and Love Emacs - Aaron Bieber(2015)](
  374. * Aaron Bieber from Wayfair is back to talk to us about his recent experience using Emacs (what?!?!). That's right, Emacs. Aaron decided it was time to see how things looked on the other side and will share what he found, what he missed from Vim, and maybe even a few things we can bring back to Vim from Emacs.
  375. * **General**
  376. * [Bandit - OvertheWire](
  377. * "The Bandit wargame is aimed at absolute beginners. It will teach the basics needed to be able to play other wargames."; It's also an effective way to learn the basics of linux and how to use the linux cli.
  378. * [The art of the command line](
  379. * Master the command line, in one page
  380. * [Stupid Unix Tricks - Jeffrey Paul](
  381. * [Why Learn AWK? - Jonathan Palardy](
  382. * [Applying Your Linux Skills to macOS: Terminal BASH and Common Commands - Jason Eckert](
  383. * [Linux Command Line](
  384. * Introduction to Linux commands and Shell scripting
  385. * [Linux Productivity Tools](
  386. * Highly recommend.
  387. * [Don Libes' Expect: A Surprisingly Underappreciated Unix Automation Tool - Robert Elder](
  388. * [mastering-zsh](
  389. * **Videos**
  390. * [Linux Command Line Dojo with Hal Pomeranz(BHIS 2020)](
  391. * In this webcast, we have our friend Hal Pomeranz sharing his massive knowledge on Linux. If you’re new to Linux, or if you know it and just want to hear from Hal’s years of using and teaching all things Linux, then this is the webcast for you.
  392. * [Part 2](
  393. * [Out With the Old, In With the GNU - Lsly(Bsides Philadelphia2017)](
  394. * In our field and related subsections, we typically don,t learn from scratch. Instead, we learn from those who have been around longer through books, online resources, and person-to-person training. That said, when is "tribal knowledge" harmful? Can we improve (or remove) commands we use for a single purpose for something better? Why do people confine their use of `awk` when it can be as flush as Perl? This talk will review some simple ways we can streamline command line, by stripping down to the bare essentials. Most examples will be for Linux, however it will touch on BSD and other command line-friendly OS'.
  395. * **Tools**
  396. * [](
  397. * explainshell is a tool (with a web interface) capable of parsing man pages, extracting options and explain a given command-line by matching each argument to the relevant help text in the man page.
  398. * [A little collection of cool unix terminal/console/curses tools](
  399. * [Pexpect](
  400. * Pexpect is a Pure Python Expect-like module
  401. * [Chepy](
  402. * Chepy is a python lib/cli equivalent of the awesome CyberChef tool.
  403. * **Windows**
  404. * **Articles/Resources**
  405. * [Keyboard shortcuts in Windows -](
  406. * **Tools**
  407. * [Chocolatey](
  408. * "The Package Manager for Windows."
  409. * **Windows cmd.exe**
  410. 1. [Windows Command-Line: Backgrounder - Rich(2018)](
  411. 2. [Windows Command-Line: The Evolution of the Windows Command-Line](
  412. 3. [Windows Command-Line: Inside the Windows Console](
  413. 4. [Windows Command-Line: Introducing the Windows Pseudo Console (ConPTY)](
  414. 5. [Windows Command-Line: Unicode and UTF-8 Output Text Buffer](
  415. * **Critical Thinking** <a name="critthink"></a>
  416. * [How to Apply Critical Thinking Using Paul-Elder Framework - designorate](
  417. * [Paul-Elder Critical Thinking Framework - University of Louisville](
  418. * **Common Vulnerability Scoring System(CVSS)** <a name="cvss"></a>
  419. * [Common Vulnerability Scoring System version 3.1: User Guide -](
  420. * [Common Vulnerability Scoring System version 3.1: Specification Document -](
  421. * **Data Breaches** <a name="breaches"></a>
  422. * [SecurityBreach](
  423. * Crowdsourced catalog of security breaches.
  424. * **Fundamental Papers** <a name="fund"></a>
  425. * [END-TO-END ARGUMENTS IN SYSTEM DESIGN - J.H. Saltzer, D.P. Reed and D.D. Clark](
  426. * This paper presents a design principle that helps guide placement of functions among the modules of a distributed computer system. The principle, called the end-to-end argument, suggests that functions placed at low levels of a system may be redundant or of little value when compared with the cost of providing them at that low level. Examples discussed in the paper include bit error recovery, security using encryption, duplicate message suppression, recovery from system crashes, and delivery acknowledgement. Low level mechanisms to support these functions are justified only as performance enhancements.
  427. * [Ceremony Design and Analysis - Carl Ellison](
  428. * Abstract. The concept of ceremony is introduced as an extension of the concept of network protocol, with human nodes alongside computer nodes and with communication links that include UI, human-to-human communication and transfers of physical objects that carry data. What is out-of-band to a protocol is in-band to a ceremony, and therefore subject to design and analysis using variants of the same mature techniques used for the design and analysis of protocols. Ceremonies include all protocols, as well as all applications with a user interface, all workflow and all provisioning scenarios. A secure ceremony is secure against both normal attacks and social engineering. However, some secure protocols imply ceremonies that cannot be made secure.
  429. * [How Complex Systems Fail (Being a Short Treatise on the Nature of Failure; How Failure is Evaluated; How Failure is Attributed to Proximate Cause; and the Resulting New Understanding of Patient Safety) Richard I. Cook, MD](
  430. * [No Silver Bullet -](
  431. * [A Mathematical Theory of Communication - Claude E. Shannon](
  432. * [The Diamond Model of Intrusion Analysis - Sergio Caltagirone, Andrew Pendergast, Christopher Betz](
  433. * **Beyond Corp**
  434. * [BeyondCorp](
  435. * [How Google Adopted BeyondCorp](
  436. * [Part 2](
  437. * [Part 3](
  438. * [Part 4](
  439. * [BeyondCorp: A New Approach to Enterprise Security - Rory Ward, Betsy Beyer](
  440. * Virtually every company today uses firewalls to enforce perimeter security. However, this security model is problematic because, when that perimeter is breached, an attacker has relatively easy access to a company’s privileged intranet. As companies adopt mobile and cloud technologies, the perimeter is becoming increasingly difficult to enforce. Google is taking a different approach to network security. We are removing the requirement for a privileged intranet and moving our corporate applications to the Internet.
  441. * **General Good Stuff** <a name="ggs"></a>
  442. * [Mozilla Enterprise Information Security](
  443. * [Rating Infosec Relevant Masters Programs - netsecfocus](
  444. * [Salted Hash Ep 34: Red Team vs. Vulnerability Assessments - CSO Online](
  445. * Words matter. This week on Salted Hash, we talk to Phil Grimes about the differences between full Red Team engagements and vulnerability assessments
  446. * [Words Have Meanings - Dan Tentler - CircleCityCon 2017](
  447. * [C2 Wiki - Security](
  448. * [Not Even Close, The State of Computer Security w/ slides - James Mickens](
  449. * [(Deliberate) practice makes perfect: how to become an expert in anything - Aytekin Tank](
  450. * [Information Security Mental Models - Chris Sanders](
  451. * [The Submarine (Article)- Paul Graham](
  452. * [Satya Nadella ‘Reads’/‘Games’ Hacker News - KicksCondor]('reads''games'-hacker-news/)
  453. * [](
  454. * [Art as a Methodology for Security Research - Leigh-Anne Galloway](
  455. * [The Natural Life Cycle of Mailing Lists - Kat Nagel](
  456. * **Helping Others** <a name="helpo"></a>
  457. * [Internet Safety for Teens, Kids, and Students -](
  458. * [STOP. THINK. CONNECT. ™ Toolkit - DHS](
  459. * [What I Learned Trying To Secure Congressional Campaigns - idlewords](
  460. * **History** <a name="history"></a>
  461. * [Collections: The Siege of Gondor, Part II: These Beacons are Liiiiiiit - Bret Devereaux](
  462. * Defense in depth aint new
  463. * [CyberInsecurity: The Cost of Monopoly - How the Dominance of Microsoft's Products Poses a Risk to Security - Daniel Geer, Charles P. Pfleeger, Bruce Schneier, John S. Quarterman, Perry Metzger, Rebecca Bace, and Peter Gutmann](
  464. * [Ford Pinto -](
  465. * [A Case Study of Toyota Unintended Acceleration and Software Safety - Phil Koopman](
  466. * [The Hacker Crackdown - Wikipedia](
  467. * The book discusses watershed events in the hacker subculture in the early 1990s. The most notable topic covered is Operation Sundevil and the events surrounding the 1987–1990 war on the Legion of Doom network: the raid on Steve Jackson Games, the trial of "Knight Lightning" (one of the original journalists of Phrack), and the subsequent formation of the Electronic Frontier Foundation. The book also profiles the likes of "Emmanuel Goldstein" (publisher of 2600: The Hacker Quarterly), the former assistant attorney general of Arizona Gail Thackeray, FLETC instructor Carlton Fitzpatrick, Mitch Kapor, and John Perry Barlow.
  468. * [The Hacker Crackdown: Law and Disorder on the Electronic Frontier by Bruce Sterling - Project Gutenberg](
  469. * **How to Ask Better Questions** <a name="bq"></a>
  470. * [How To Ask Questions The Smart Way - Eric Raymond](
  471. * [Socratic questioning - Wikipedia](
  472. * [The Six Types Of Socratic Questions -](
  473. * [Ask Good Questions: Deep Dive - Yousef Kazerooni](
  474. * [Relearning the Art of Asking Questions - HBR](
  475. * [How To Ask Questions The Smart Way -](
  476. * **Information Processing** <a name="ip"></a>
  477. * [Drinking from the Fire Hose: Making Smarter Decisions Without Drowning in Information - Book](
  478. * [How to make sense of any mess - Abby Covert](
  479. * **Learning** <a name="learning"></a>
  480. * **101**
  481. * [Autodidacticism - Wikipedia](
  482. * [Effective learning: Twenty rules of formulating knowledge - SuperMemo](
  483. * [Learning How to Learn: Powerful mental tools to help you master tough subjects - Coursera](
  484. * [Double-loop Learning - Wikipedia](
  485. * Double-loop learning entails the modification of goals or decision-making rules in the light of experience. The first loop uses the goals or decision-making rules, the second loop enables their modification, hence "double-loop". Double-loop learning recognises that the way a problem is defined and solved can be a source of the problem. This type of learning can be useful in organizational learning since it can drive creativity and innovation, going beyond adapting to change to anticipating or being ahead of change.
  486. * [DIKW pyramid - Wikipedia](
  487. * [Bloom’s Taxonomy - Vanderbilt University Center for Teaching](
  488. * **Articles/Blogposts/Writeups**
  489. * [Janki Method — Using SRS to Improve Programming - Jack Kinsella](
  490. * Using spaced repetition systems to learn and retain technical knowledge.
  491. * [Janki Method Refined - Tips, shortcuts and revisions to the original method](
  492. * [The Motivation Secret: How to Maintain Intense Motivation as a Hacker (or Anything) - Luke Stephens](
  493. * [Deliberate Practice: What It Is and How to Use It - James Clear](
  494. * [The Importance Of Deep Work & The 30-Hour Method For Learning A New Skill - Azeria](
  495. * [The idea of a difficulty curve is all wrong - David Strachan](
  496. * [How to Read a Book, v5.0 - Paul N. Edwards University of Michigan](
  497. * [How to Read a Book - Wikipedia](
  498. * [Learning to Learn - Nick Agliano(2020)](
  499. * [Please stop asking for “advanced” learning content - Don Jones(2020)](
  500. * **Talks/Presentations/Videos**
  501. * [Continuous Skills Improvement For Everyone - Matt Scheurer(OISF19)](
  502. * [Develop Technical Recall Skills: Spaced Repetition with Anki w/ Josh Wright(2020)](
  503. * If you're like Josh, you may be overwhelmed with the amount of knowledge you're supposed to learn and recall at a moment's notice. There's an interesting science behind our human ability to learn and recall technical information, and with some best-practices you can apply to improve your recall and memorization skills. Whether you're studying for a certification exam, undertaking self-paced training online, or preparing to participate in an online class, you're going to be challenged to learn and remember technical concepts. In this Hackin' Cast Josh covers the amazing Anki tool, and how you can apply spaced repetition to develop long-term recall for any technical subject.
  504. * **Papers**
  505. * [Retrieval-Based Learning: A Perspective for Enhancing Meaningful Learning - Jeffrey D. Karpicke, Phillip J. Grimaldi(2012)](
  506. * [Retrieval-Based Learning:An Episodic Context Account - Jeffrey D. Karpicke, Melissa Lehman, William R. Aue(2014)](
  507. * **Excel**
  508. * [You Suck at Excel with Joel Spolsky(2015)](
  509. * The way you are using Excel causes errors, creates incomprehensible spaghetti spreadsheets, and makes me want to stab out my own eyes. Enough of the =VLOOKUPs with the C3:$F$38. You don't even know what that means.
  510. * [Notes](
  511. * **Agnostic Tools**
  512. * [Structured Text Tools](
  513. * The following is a list of text-based file formats and command line tools for manipulating each.
  514. * **Videos**
  515. * [jumpcutter](
  516. * Automatically edits vidx. [Explanation here](
  517. * [Auto-Editor](
  518. * Auto-Editor is a video editing tool that can automatically edit raw source video into a entertaining and polished video. It works by analyzing the video's audio to detect when a section needs to be cut, kept in, or zoomed in, then auto-editor runs a subprocess called ffmpeg to create the new video.
  519. * [cut-the-crap](
  520. * Cut the crap is an automatic video editing program for streamers. It can cut out uninteresting parts by detecting silences. This was inspired by jumpcutter, where this program can get better quality results by using an (optional) dedicated microphone track. This prevents cutting of quieter consonants for example. Using ffmpeg more efficiently also produces faster results and is less error prone.
  521. * **Learning New Things**
  522. * [The Paradox of Choice: Learning new skills in InfoSec without getting overwhelmed - AzeriaLabs](
  523. * **Metrics** <a name="metrics"></a>
  524. * [Be Careful What You Measure - Mark Graham Brown](
  525. * [How to Use Metrics - George K. Campbell(2006)](
  526. * [Security metric techniques: How to answer the 'so what?' - Bill Brenner](
  527. * [Security Value Made Visible: How American Water's Bruce Larson uses a simple metric to build bridges with business partners and justify security spending at the same time - Scott Berinato](
  528. * [A key performance indicator for infosec organizations: Using probabilistic risk KPIs to direct complex risk engineering efforts - Ryan McGeehan(2019)](
  529. * **Networking** <a name="networking"></a>
  530. * [The Bits and Bytes of Computer Networking - Google/Coursera](
  531. * This course is designed to provide a full overview of computer networking. We’ll cover everything from the fundamentals of modern networking technologies and protocols to an overview of the cloud to practical applications and network troubleshooting. By the end of this course, you’ll be able to: describe computer networks in terms of a five-layer model; understand all of the standard protocols involved with TCP/IP communications; grasp powerful network troubleshooting tools and techniques; learn network services like DNS and DHCP that help make computer networks run; understand cloud computing, everything as a service, and cloud storage
  532. * [Linux Network Administration -](
  533. * One(really long) page reference
  534. * [IPv4/v6 Subnet Mask cheatsheet -](
  535. * **Normalization of Deviance** <a name="nom"></a>
  536. * [The normalization of deviance in healthcare delivery - John Hanja](
  537. * Many serious medical errors result from violations of recognized standards of practice. Over time, even egregious violations of standards of practice may become “normalized” in healthcare delivery systems. This article describes what leads to this normalization and explains why flagrant practice deviations can persist for years, despite the importance of the standards at issue. This article also provides recommendations to aid healthcare organizations in identifying and managing unsafe practice deviations before they become normalized and pose genuine risks to patient safety, quality care, and employee morale.
  538. * **Problem Solving** <a name="ps"></a>
  539. * [Software Problem Solving Cheat Sheet - Florian Roth](
  540. * [The XY Problem](
  541. * The XY problem is asking about your attempted solution rather than your actual problem. This leads to enormous amounts of wasted time and energy, both on the part of people asking for help, and on the part of those providing help.
  542. * [The AZ Problem](
  543. * This website introduces the AZ Problem: a generalization of the XY Problem. To wit, if we agree that the XY Problem is a problem, than the AZ Problem is a metaproblem. And while the XY Problem is often technical, the AZ Problem is procedural. The AZ Problem is when business requirements are misunderstood or decontextualized. These requirements end up being the root cause of brittle, ill-suited, or frivolous features. An AZ Problem will often give rise to several XY Problems.
  544. * [SCQA – A Framework For Defining Problems & Hypotheses - Paul(](
  545. * **Project Management** <a name="pms"></a>
  546. * **101**
  547. * [Project management - Wikipedia](
  548. * [What is Project Management? - Project Management Institute](
  549. * [CrimeOps: The Operational Art of Cyber Crime - The Grugq](
  550. * **Agile**
  551. * [An Agile Primer - Daniel Miessler(2020)](
  552. * **Gantt Charts**
  553. * [Gantt Chart - Wikipedia](
  554. * [The Ultimate Guide to… Gantt Charts -](
  555. * **Lean/Toyota Production System**
  556. * [Toyota Production System - Wikipedia](
  557. * The Goal, The Phoenix Project
  558. * **Tools**
  559. * [A simplified Jira clone built with React and Node](
  560. * **Ransomware** <a name="ransomware"></a>
  561. * [The Trade Secret: Firms That Promised High-Tech Ransomware Solutions Almost Always Just Pay the Hackers - Renee Dudley and Jeff Kao(2019)](
  562. * **Regular Expressions** <a name="regex"></a>
  563. * [Regular Expressions | A Complete Beginners Tutorial - Atmanand Nagpure](
  564. * [Fall in love with Regex — Why don’t you marry them? - Sarvagya Sagar(2019)](
  565. * [Regular Expressions (Regex) Overview - Matt Scheurer(Derbycon 2017)](
  566. * Writing Regular Expressions (Regex) is a versatile skill set to have across the IT landscape. Regex has a number of information security related uses and applications. We are going to provide an overview and show examples of writing Regex for pattern matching and file content analysis using sample threat feed data in this presentation. Along with a healthy dose of motherly advice, we cover Regex syntax, character classes, capture groups, and sub-capture groups. Whether Regex is something completely new or worth brushing up on, this talk is geared toward you.
  567. * **Research** <a name="research"></a>
  568. * **Doing/Performing Research**
  569. * [Research Debt - Chris Olah, Shan Carter](
  570. * [Ten Simple Rules for Doing Your Best Research, According to Hamming](
  571. * [Feynman’s Breakthrough, Disregard Others! - stepsandleaps](
  572. * [On Doing Research -](
  573. * [Follow Your Curiosity. Read Your Ass Off. - Andy Sparks(2020)](
  574. * **Legalities**
  575. * [A Researcher’s Guide to SomeLegal Risks of Security Research - Sunoo Park, Kendra Albert(2020)]()
  576. * What does it cover? This guide overviews broad areas of potential legal riskrelated to security research, and the types of security research likely implicated.We hope it will serve as a useful starting point for concerned researchers andothers. While the guide covers what we see as the main areas of legal risk forsecurity researchers, it is not exhaustive. It also doesn’t create a lawyer-clientrelationship between you and the authors. This guide focuses on U.S. law, and mostly federal law.Different U.S. statesand jurisdictions may have different laws, and even different interpretations ofthe same federal law. This guide does not do a state-by-state analysis, butrather focuses on federal law and how it is interpreted by most states. Todetermine which states’ law applies to your specific situation, consult a lawyer.This guide doesnotdiscuss risks associated with security research undernon-U.S. legal systems. Your activity may raise legal risks in legal systemsoutside of the U.S. if it takes place or has impacts outside the U.S., or involvesor impacts people who are governed by non-U.S. legal systems. Similarly, youractivity may be subject to U.S. legal liability (as well as liability under yourlocal law) even if it occurs primarily outside the U.S., if it has impacts in theU.S. or involves or involves U.S. people and/or equipment.2Finally, if your research involves human subjects and is aiming to pro-duce generalizable knowledge,3you should consult an institutional review board(IRB) or ethical review committee to ensure that you are in compliance withhuman testing rules, which are outside the scope of this Guide
  577. * **Request for Service/Product** <a name="rfsp"></a>
  578. * [Information Security Assessment RFP Cheat Sheet - Lenny Zeltser](
  579. * **Risk** <a name="risk"></a>
  580. * See [Threat Modeling](./
  581. * [Factor analysis of information risk (FAIR)- Wikipedia](
  582. * Factor Analysis of Information Risk (FAIR) is a taxonomy of the factors that contribute to risk and how they affect each other. It is primarily concerned with establishing accurate probabilities for the frequency and magnitude of data loss events. It is not a methodology for performing an enterprise (or individual) risk assessment.
  583. * **Securing yourself** <a name="secself"></a>
  584. * [Operation Luigi: How I hacked my friend without her noticing](
  585. * My friend gave me permission to "hack all her stuff" and this is my story. It's about what I tried, what worked, my many flubs, and how easy it is to compromise Non Paranoid People TM.
  586. * [Blogpost](
  587. * **Software Testing** <a name="softwaretesting"></a>
  588. * **Articles/Blogposts/Writeups**
  589. * [What broke the bank - Chris Stokel-Walker(2019)](
  590. * A disastrous IT migration corrupted 1.3 billion customer records. The culprit was insufficient testing.
  591. * **Talks/Presentations**
  592. * [When to Test and How to Test It - Bruce Potter - Derbycon7](
  593. * “I think we need a penetration test” This is one of the most misunderstood phrases in the security community. It can mean anything from “Someone should run a vulnerability scan against a box” to “I’d like nation-state capable actors to tell me everything that wrong with my enterprise” and everything in between. Security testing is a complex subject and it can be hard to understand what the best type of testing is for a given situation. This talk will examine the breadth of software security testing. From early phase unit and abuse testing to late phase penetration testing, this talk will provide details on the different tests that can be performed, what to expect from the testing, and how to select the right tests for your situation. Test coverage, work effort, attack simulation, and reporting results will be discussed. Also, this talk will provide a process for detailed product assessments, i.e.: if you’ve got a specific product you’re trying to break, how do you approach assessing the product in a way that maximizes your chance of breaking in as well as maximizing the coverage you will get from your testing activity.
  594. * **Having a Pentest Performed**
  595. * [Red Team Assessment and Penetration Testing - Manga Sridhar Akella](
  596. * [Pen Tests and Red Teams are NOT the same - Carole Theriault](
  597. * [Putting your security assessment budget on a leash while avoiding the Pentest Puppy Mill - John Strand, Paul Asadoorian(2013)](
  598. * The goal of a penetration test should be to elevate your security, not line the pocket of the pentester. In this webcast, Paul and John discuss ways to structure your pentest so that you aren't paying for shells from a Pentest Puppy Mill, but instead paying for reproducible results that will provide a baseline for future testing.
  599. * [What to Expect When You're Expecting a Penetration Test - CJ Cox & Bryan Strand(2020)](
  600. * **Scoping**
  601. * [Scoping a pentest - PentesterLab](
  602. * **Shopping for Testing**
  603. * [Don’t end up with a pencil: Tips for shopping for pen tests. - Dmitry Zadadsky(BSidesBoston2020)](
  604. * As a blue team, penetration tests are a critical part of your security program and finding a pen test company that can meet your needs is paramount. Unfortunately, there is no manual for hiring a pen tester. Sometimes you need to learn from mistakes and successes. This presentation will go over the experience of a penetration test from the customer’s perspective. You’ll hear stories of tests that were good, bad, and ugly. First, you need to determine what your goals are to pick the right kind of assessment. Then you can start looking at vendors. Asking some of the right questions beforehand can really set the stage for success. Contracts, scoping, and documentation can be a pain, but they are important. We will go over the things you want to cover. Afterward comes the report. What should you do if there are lots of findings? What if there aren’t any? We will cover answers to these and more to help make sure when you buy a pen test, you don’t end up with a pencil.
  605. * **Vulnerability Assesssment**
  606. * [Vulnerability Assessment 2.0 - John Askew(Derbycon 2014)](
  607. * What can you do to step up your game as a security analyst? Vulnerability scanners and other security assessment tools can be extremely useful for collecting information quickly and efficiently, but what are some good next steps for analyzing and using that information? How much value does a raw vulnerability scan report provide (hint: don’t just hand this to a client or supervisor), and how much more value can we get out of our tools with a little bit of effort? What do you do when you need data that an existing tool can’t provide? John will discuss some areas in the security asssessment process that are ripe for easy wins through custom scripting, including data aggregation, diffing, false,positive identification, and visualization. As an example, John will release a tool for slicing and dicing the results from assessment tools in interesting ways, based on various techniques used in previous consulting engagements.
  608. * **Statistics** <a name="statistics"></a>
  609. * [How to Lie with Statistics, Information Security Edition - Tony Martin-Vegue(Circle City Con2018)](
  610. * Stiff statistics, prismatic pie charts, and questionable survey results drown the Information Security space in a sea of never-ending numbers that can be difficult to sift through. Have you ever finished reading a research institution's annual security report and felt your Spidey sense begin to tingle with doubt or disbelief? What you are probably sensing is a manipulation of statistics, an age-old hoodwink that has been occurring as long as numbers have been used to convey information. This critical subject was first examined over 60 years ago, when Darrell Huff first published the groundbreaking book "How to Lie with Statistics," over 60 years ago. This presentation takes the foundation Huff created and updates the core concepts for the contemporary Information Security field. Most people would be shocked to find that data is often manipulated to lead the reader to a particular conclusion. Several areas are examined: bias in vendor-sponsored security reports, data visualization misuse and common security fallacies. There is a silver lining - once you are aware of the subtle ways data is manipulated, it's easy to spot. Attendees will walk away with a new understanding of ways to identify and avoid unintentionally using some of the methods described.
  611. * **System Design** <a name="systemdesign"></a>
  612. * [The System Design Primer](
  613. * Learning how to design scalable systems will help you become a better engineer. System design is a broad topic. There is a vast amount of resources scattered throughout the web on system design principles. This repo is an organized collection of resources to help you learn how to build systems at scale.
  614. * **TableTop Exercises** <a name="ttx"></a>
  615. * [Why Crisis management exercises (still) work - Mercedes M Diaz(2020)](
  616. * [Intro to Tabletop Exercises with Amanda Berlin & Jeremy Mio(2020)](
  617. * When testing responses, defenses, and detections of an environment one of the main tools that can be used is a tabletop exercise. A tabletop exercise is a meeting of key stakeholders and staff who walk step by step through the mitigation of some type of disaster, malfunction, attack, or other emergency in a low stress situation. In this short training webinar, we walk through two basic exercises from beginning to end, covering what helpful structure, items, and activities should be included. We then follow up each exercise with an after action report to recap.
  618. * **Task Automation** <a name="automation"></a>
  619. * [WALKOFF](
  620. * WALKOFF is a flexible, easy to use, automation framework allowing users to integrate their capabilities and devices to cut through the repetitive, tedious tasks slowing them down,
  621. * [StackStorm](
  622. * [Robot Framework](
  623. * Robot Framework is a generic open source automation framework for acceptance testing, acceptance test driven development (ATDD), and robotic process automation (RPA). It has simple plain text syntax and it can be extended easily with libraries implemented using Python or Java. Robot Framework is operating system and application independent. The core framework is implemented using Python, supports both Python 2 and Python 3, and runs also on Jython (JVM), IronPython (.NET) and PyPy. The framework has a rich ecosystem around it consisting of various generic libraries and tools that are developed as separate projects. For more information about Robot Framework and the ecosystem, see
  624. * **Tools to Know About** <a name="ttka"></a>
  625. * [Process Monitor X v2](
  626. * Procmon-like tool that uses Event Tracing for Windows (ETW) instead of a kernel driver to provide event information.
  627. * [rga: ripgrep, but also search in PDFs, E-Books, Office documents, zip, tar.gz, etc. - phiresky](
  628. * [Introduction To Metasploit – The Basics](
  629. * [Shodan](
  630. * [agrep](
  631. * print lines approximately matching a pattern
  632. * **Vendor Security** <a name="vensec"></a>
  633. * [UC Berkely Vendor Security Assessment Program](
  634. * [VSAQ: Vendor Security Assessment Questionnaire](
  635. * VSAQ is an interactive questionnaire application. Its initial purpose was to support security reviews by facilitating not only the collection of information, but also the redisplay of collected data in templated form. At Google, questionnaires like the ones in this repository are used to assess the security programs of third parties. But the templates provided can be used for a variety of purposes, including doing a self-assessment of your own security program, or simply becoming familiar with issues affecting the security of web applications.
  636. * **The Web** <a name="web"></a>
  637. * [Web Architecture 101 - Jonathan Fulton](
  638. * [The Tangled Web - Michal Zalewski(book)](
  639. * "The Tangled Web is my second book, a lovingly crafted guide to the world of browser security. It enters an overcrowded market, but there are two reasons why you may want to care. First of all, where other books simply dispense old and tired advice on remediating common vulnerabilities, The Tangled Web offers a detailed and thoroughly enjoyable account of both the "how" and the "why" of the modern web. In doing so, it enables you to deal with the seedy underbelly of contemporary, incredibly complex web apps. The other reason is that it is based on years of original research - including, of course, my Browser Security Handbook (2008). I think it is simply unmatched when it comes to the breadth and the quality of the material presented. It outlines dozens of obscure but remarkably important security policies, governing everything from content rendering to frame navigation - and affecting your applications in more ways than you may expect."
  640. * **Tools**
  641. * [Firefox Developer Tools - MDN](
  642. * Firefox Developer Tools is a set of web developer tools built into Firefox. You can use them to examine, edit, and debug HTML, CSS, and JavaScript. This section contains detailed guides to all of the tools as well as information on how to debug Firefox for Android, how to extend DevTools, and how to debug the browser as a whole.
  643. * [Chrome DevTools -](
  644. * [Discover DevTools](
  645. * Learn how Chrome DevTools can sharpen your dev process and discover the tools that can optimize your workflow and make life easier.
  646. * **Zero Trust** <a name="zerotrust"></a>
  647. * **Articles/Blogposts/Writeups**
  648. * [Exploring The Zero Trust Model -](
  649. * [Awesome Zero trust](
  650. * **Talks/Presentations/Videos**
  651. * **Fun** <a name="fun"></a>
  652. * [Welcome to Infosec (Choose your own Adventure) - primarytyler](
  653. * [Choose Your Own Red Team Adventure - Tim Malcomvetter](