What's next after season 2?

About this Episode

In the grand wrap-up of season two of the podcast 'Your Cyber Path', hosts Kip Boyle and Jason Dion reflect on their four-year podcast journey. They also reveal that for the time being, there won't be a season three as originally planned.

Several factors have influenced this decision, the primary being their venture Akylade – a cybersecurity certification organization. They're also experiencing increased demand for their time and energy due to factors involving Akylade and other projects. However, they highlight the intention of potentially doing a third season in the future based on the feedback and demand received.

Kip Boyle will continue to mentor notes but change the frequency from weekly to monthly. Jason Dion urges listeners to check their cybersecurity course, 'Irresistible' on Udemy.

They greatly encourage listeners to stay in touch and seek guidance on cybersecurity careers through email which is available at yourcyberpath.com.

Relevant websites for this episode

https://cr-map.com

https://www.akylade.com

https://www.yourcyberpath.com

https://www.diontraining.com/udemy

SDP 10: Separation of Privileges

About this Episode

In this episode of the Your CyberPath podcast, Kip Boyle and Jason Dion delve into the concept of the separation of privilege as a vital component of their series on security architecture and design principles.

Jason and Kip talk about how the separation of privilege illustrates its significance through real-world examples. They also help showcase its application in technologies, military operations, and financial transactions.

Jason also draws from his military experience to underscore the critical role of separation of privilege in SOVOT (System Operations Verification and Testing) environments.

Finally, they underscore its importance in password management systems. They emphasize its pivotal role in upholding cybersecurity standards. Understanding these principles is essential for building robust security frameworks.

Relevant websites for this episode

The NIST Separation of Duty (SOD) - https://csrc.nist.gov/glossary/term/separation_of_duty

Other relevant Episodes

EP 94: Ten Security Design Principles (SDP)

EP 96: SDP 1: Least Privilege

EP 98: Security Design Principles 2: Psychological Acceptability

EP 101: SDP 3: Economy of Mechanism

EP 103: SDP 4 Compromise Recording

EP 105: SDP 5: Work Factor

EP 107: SDP 6: Failsafe Defaults

EP 109: SDP 7: Complete Mediation

EP 111: SDP 8 open Design

EP 113: SDP 9 — Least Common Mechanism

About this episode

In this episode, Kip Boyle and Jason Dion discuss the importance of cybersecurity in the current digital landscape and focus on comparing two different standards: The NIST Cybersecurity Framework and the CIS Top 18.

The NIST Framework was created to assist organizations in becoming cyber resilient and offers an adaptable and comprehensive approach to cyber risks. The CIS Top 18, on the other hand, provides an actionable and practical checklist of controls that is prioritized and sequenced.

Both of these frameworks provide us with cybersecurity measures that can be used for different applications. They can be used individually, or they can work together by complementing each other in a comprehensive cybersecurity strategy.

It is important to realize that the CIS Top 18 can end up being quite expensive for smaller organizations to operate, though, which is why many people are choosing the NIST CSF instead. You should always consider various factors, such as organizational size and specific needs, the type of threats faced, and the budget available for implementation when selecting the framework for your organization.

Relevant websites for this episode

The NIST Cyber Security Framework (CSF) - https://www.nist.gov/cyberframework

The 18 CIS Critical Security Controls - https://www.cisecurity.org/controls/cis-controls-list

Other Relevant Episodes

EP 62 – The NIST Cybersecurity Framework

EP 79 – Mid-Career Transition Success Story with Steve McMichael

EP 83 – Automating NIST Risk Management Frameowrk with Rebecca Onuskanich

In this episode, Kip and Jason cover the Security Design Principle of “Least Common Mechanism”.

The Lease Common Mechanism is the ninth security design principle and focuses on how you can best protect older, legacy systems in large organizations and within the government.

Security Design Principle #9 is a crucial concept in the field of cybersecurity. It advocates for minimizing the amount of mechanisms shared by different users or processes, thereby reducing the chances of a security breach. This principle is rooted in the idea that shared resources or functionalities can become potential vulnerabilities, especially if they are used by multiple entities with varying levels of trustworthiness.

The principle is based on the understanding that any shared mechanism or resource is a potential attack surface. When different programs or users rely on the same functionality or data paths, a breach in one can easily become a gateway to compromise the others. For instance, if a shared library has a vulnerability, every program using that library is at risk. Therefore, by reducing the number of shared components, the principle of Least Common Mechanism aims to limit the potential damage that can be caused by a security flaw or breach.

Implementing this principle involves designing systems where the functionalities are as isolated as possible. This can be achieved through techniques like sandboxing, where programs run in isolated environments, or through the use of microservices architectures, where applications are broken down into smaller, independent services. Each service or program having its unique mechanisms greatly diminishes the risk of a widespread security incident.

The principle also underlines the importance of not only securing shared resources but also constantly monitoring them. Regular audits and updates of shared components are vital to ensure they remain secure. In essence, the Least Common Mechanism principle is about understanding the risks associated with shared resources and proactively designing systems to minimize these risks.

Relevant websites for this episode

• Akylade Certified Cyber Resilience Fundamentals (A/CCRF)
• Your Cyber Path

Other Relevant Episodes

• Episode 96 – SDP 1 – Least Privilege
• Episode 98 – SDP 2 – Psychological Acceptability
• Episode 101 – SDP 3 – Economy of Mechanism
• Episode 103 – SDP 4 – Compromise Recording
• Episode 105 – SDP 5 – Work Factor
• Episode 107 – SDP 6 – Failsafe Defaults
• Episode 109 – SDP 7 – Complete Mediation
• Episode 111 - SDP 8 – Open Design

https://www.yourcyberpath.com/112/

In this episode, Kip and Jason jump into answer questions directly from our listeners!

We share valuable advice and insights into starting and advancing in the cybersecurity field by addressing ways to overcome some common challenges such as imposter syndrome, applying skills from diverse industries, and filling employment history gaps. 

Further, you will get some guidance on gaining relevant experience, understanding job roles, tackling age bias, and displaying self-confidence to potential employers. 

We will then culminate with some valuable tips on overcoming technical skill gaps and making successful career transitions, alongside with coverage of the HIRED course and its transition from a high-cost masterclass to a more accessible Udemy course that anyone can participate in.

• How do I get started in cybersecurity?
• How can I gain experience?
• How to I transition into cybersecurity later in life?
• How do I identify my desired job and current transferrable skills?
• How should I address a gap in my resume?
• How can I deal with imposter syndrome?

Relevant websites for this episode

• Akylade Certified Cyber Resilience Fundamentals (A/CCRF)
• Your Cyber Path
• IRRESISTIBLE: How to Land Your Dream Cybersecurity Position
• The Cyber Risk Management Podcast

Other Relevant Episodes

• Episode 90 - How to Get Your First Job as a Pentester with Chris Horner
• Episode 45 - Live Resume Review
• Episode 24 - How to Navigate a Skill Gap
• Episode 66 - How to Be Irresistible to Hiring Managers

https://www.yourcyberpath.com/111/

In this episode, Kip and Jason delve into the specific security design principle of Open Design.

Open Design does not equate to open-source software but refers to transparency in revealing the mechanisms and inner workings of security controls.

The hosts discuss the misconceptions surrounding Open Design, emphasizing that it does not require disclosing source code but rather the transparency of security mechanisms. They also stress that Open Design encourages outsiders to review and provide feedback, ultimately enhancing the security of the system.

Kip shares an example of an inadequate disclosure of a company’s security architecture which prompted him to switch to another vendor, which offered more transparency.

Jason mentions the concept of "security by obscurity," and explains that while obscurity can provide some level of protection, it is not sufficient, as attackers can easily bypass such measures with scanning tools.

The hosts suggest that getting involved in Open Design initiatives can help individuals break into the cybersecurity field and gain recognition, urging interested parties to participate in open standards development processes, such as the creation of industry certifications, to establish credibility and build their careers.

What You’ll Learn

●    What is open design?

●    What are the common misconceptions surrounding open design?

●     What does the concept of “security by obscurity” mean?

●     How can you break into cybersecurity with open design?

Relevant Websites For This Episode

●    Akylade Certified Cyber Resilience Fundamentals (A/CCRF)

●  Your Cyber Path

●  IRRESISTIBLE: How to Land Your Dream Cybersecurity Position

●  The Cyber Risk Management Podcast

Other Relevant Episodes

●   Episode 92 - Password Managers

●   Episode 89 - Getting My First Job in Cybersecurity

●   Episode 82 - From Truck Driver to Cybersecurity Analyst

https://www.yourcyberpath.com/110/

In this episode, hosts Kip Boyle and Jason Dion discuss the topic of ageism in cybersecurity careers. They address a listener's question about whether it is too late for a career change into cybersecurity at the age of 60-65. The hosts acknowledge that ageism does exist in the industry, but they provide tips and strategies for older individuals to overcome this challenge.

First, they advise career changers to identify their transferable skills and highlight them on their resumes. They also recommend choosing job titles carefully, avoiding entry-level positions that may be more suited for younger candidates. Instead, older individuals should target higher-level positions that align with their experience and expertise.

The hosts also discuss the importance of addressing ageism during the interview process. They suggest talking about new technologies and demonstrating a willingness to adapt and embrace change. Additionally, they advise older candidates to choose employers wisely, considering organizations that value and appreciate the skills and experience they bring to the table.

Overall, the episode provides practical advice for older individuals looking to transition into cybersecurity careers and navigate the challenges of ageism in the industry.

What You’ll Learn

●    Am I too old to do a career change into cybersecurity?

●   What are some strategies to overcome age-related challenges when pursuing a career change into cybersecurity?

●    Should I highlight my transferable skills when changing careers?

●    What should older individuals consider when targeting job positions in the cybersecurity field?

Relevant Websites For This Episode

●    Akylade Certified Cyber Resilience Fundamentals (A/CCRF)

●  Your Cyber Path

●  IRRESISTIBLE: How to Land Your Dream Cybersecurity Position

●  The Cyber Risk Management Podcast

Other Relevant Episodes

●  Episode 64 - How I got my first cybersecurity analyst job with Sebastian Whiting

●  Episode 66 - How to be irresistible to hiring Managers

●  Episode 38 -  Wes’ Cybersecurity Job Hunt

https://www.yourcyberpath.com/109/

In this episode, we are returning to the Security Design Principles series, this time with Complete Mediation.

Complete mediation means the system checks the user trying to access a file or perform an action is authorized to access this file or perform this action.

Complete mediation is also implemented in the security reference monitor (SRM) in Windows operating systems. The SRM checks fully and completely that a user has access to perform an action each time they try to perform it.

It also ties back to one of the three As of cybersecurity, which is Authorization, since the user has to prove having access to something when they request it.

Complete mediation can be a huge challenge to usability, and it might be something that interferes with your operations. That’s where you need to understand that the security design principles are not a compliance list and that you should use them to enhance your systems. You should not be trying to get every principle to 100%.

What You’ll Learn

●    What is complete mediation?

●    What are some examples of complete mediation?

●     How is complete mediation implemented in Windows?

●     What are the challenges of complete mediation?

Relevant Websites For This Episode

●    Akylade Certified Cyber Resilience Fundamentals (A/CCRF)

●  Your Cyber Path

●  IRRESISTIBLE: How to Land Your Dream Cybersecurity Position

●  The Cyber Risk Management Podcast

Other Relevant Episodes

●  Episode 103 - SDP 4: Compromise Recording

●  Episode 105 - SDB 5: Work Factor

●  Episode 107 -  SDP 6: Failsafe Defaults

https://www.yourcyberpath.com/108/

In this episode, we discuss a critically important topic which is Selfcare.

Cybersecurity is a great career, however it is not 100% stress free, burning out and working yourself into oblivion is very common. In this episode our hosts Jason and Kip give you some tips to make sure you have your selfcare in check.

The first thing you should do is take time off. It's common to see people who don’t take any time off, and over time it can easily get to you without you being able to realize how much your stress is building up.

Next up, always have an emergency fund. It should be between 3 to 12 months of savings.

Having this money on the side can help you get out of bad situations and maybe even have the chance to do something fun every once in a while.

The last tip we have for you is to make sure you separate self compassion from self judgment.

You need to realize that beating yourself up is really stressful and can easily drive you crazy.

Always treat yourself with patience, empathy, warmth, and understanding that you would expect from a friend.

You should always adopt a growth mindset, which can strengthen your abilities and give you much needed resilience to stress and burnout.

What You’ll Learn

●    Why is selfcare important?

●    How to handle your time off?

●    What strategy can you use to save money? 

●    How to avoid self judgment?    

Relevant Websites For This Episode

●    Akylade Certified Cyber Resilience Fundamentals (A/CCRF)

●  Your Cyber Path

●  IRRESISTIBLE: How to Land Your Dream Cybersecurity Position

●  The Cyber Risk Management Podcast

Other Relevant Episodes

●   Episode 100 - Special with Kip and Jason

●  Episode 95 - The Cybersecurity Student Perspective with Sam Bodine

●  Episode 97 - Which Certification Roadmap Or Path Should I Use?

https://www.yourcyberpath.com/107/

In this episode, we go back to the Security Design Principles series, this time we are discussing Failsafe Defaults.

Failsafe defaults simply means that the default condition of a system should always be to deny.

An example of a failsafe default is the security reference monitor (SRM) that has been implemented in Windows operating systems since Windows NT. The SRM prevents access to any actions like logging on, accessing a file, or printing something unless the user presents a token to prove that they should have access to a file or an action.

There will always be two choices for failsafe defaults - to fail close or to fail open. The DoD and government organization side will tend toward using the fail close option, while the commercial and more streamlined companies will definitely prefer to fail open.

There will always be this challenge between security and operations. More security means less operations and more inconveniences, while prioritizing operations means that security will not be the best. It all depends on your organization and its goals.

Understanding failsafe defaults and other security design principles will help you become a better analyst and produce more secure, robust, and functional systems.

What You’ll Learn

●    What is Failsafe Defaults?

●    What are some examples for Failsafe defaults?

●     What is the Security Reference Monitor?

●     What is the difference between failing close and failing open?

Relevant Websites For This Episode

●    Akylade Certified Cyber Resilience Fundamentals (A/CCRF)

●   Your Cyber Path

●   IRRESISTIBLE: How to Land Your Dream Cybersecurity Position

●   The Cyber Risk Management Podcast

Other Relevant Episodes

●   Episode 103 - SDP 4: Compromise Recording

●   Episode 105 - SDB 5: Work Factor

●   Episode 101 -   SDP 3: Economy of Mechanism