Day 2 Cloud Packet Pushers Interactive LLC

Today on Day Two Cloud we go deep on new areas of cloud security that you may not be familiar with. There are forces out there that are driving the rise of new security tools and processes.

Security issues we cover include:



* CSPM – Cloud Security Posture Management

* CWPP – Cloud Workflow Protection Platform

* CIEM – Cloud Infrastructure Entitlement Management

* CNAPP – Cloud Native Application Protection Platform



Our guest is Jo Peterson, VP Cloud and Security, at Clarify360.

Sponsor: DoiT

An award-winning strategic partner of Google Cloud and AWS, DoiT works alongside more than 3,000 customers to save them time and money. Combining intelligent software with expert consultancy and unlimited support, DoiT delivers the true promise of the cloud at peak efficiency with ease, not cost. Their technology is backed by deep multicloud expertise in the analytics, optimization and governance of cloud architecture, as well as specializations in Kubernetes, AI, and more. Learn more at doit.com.

Show Links:

@cleartechtoday – Jo Peterson on Twitter

Jo Peterson on LinkedIn

Day Two Cloud 191: Modernizing Cloud Security And Optimizing Costs With Jo Peterson – Packet Pushers

Network automation is a mess. Networks are full of dependencies, the risk of unintended consequences is high, processes are immature or non-existent, there’s a learning curve on tools, and lots of networking teams struggle to get beyond a handful of tried-and-true scripts. While cloud automation isn’t a technological utopia, it’s in a much better state than its counterpart. Can network automation catch up?
On today’s Day Two Cloud we discuss the state of  network automation and whether and how it can improve. Our guests are Chris Grundemann and Scott Robohn, co-founders of the Network Automation Forum (NAF). The NAF aims to serve as a gathering place, both online and in the real world, for network engineers, developers, and vendors to advance the state of the art by sharing informaiton and best practices, developing business cases to drive automation, and researching tools and trends.
We discuss:

* A definition of network automation
* Defining boundaries with other parts of the infrastructure stack
* How network automation got into this state
* The impact of cloud and cloud networking on network automation
* How AI and ML might affect network automation
* More

Sponsor: Drata
Automate your security framework compliance with Drata. Drata streamlines your SOC 2, ISO 27001, PCI DSS, GDPR, HIPAA, CCPA, FIEC, NIST Standards, CMMC and other compliance frameworks and provides 24-hour continuous control monitoring so you focus on scaling securely. Drata integrates with your tech stack through applications such as AWS, Azure, Github, Okta and Cloudflare. Say goodbye to manual evidence collection and hello to automated compliance by visiting drata.com/partner/daytwocloud.
Show Notes:
Network Automation Forum
SuziQ
Heavy Networking 658: Using Batfish To Model And Test Your Network – Packet Pushers
AutoCon 0
Chris Grundemann on LinkedIn
Chris Grundemann’s Blog
@ChrisGrundemann – Chris Grundemann on Twitter
Scott Robohn on LinkedIn
Transcript
Transcripts are provided best effort by an automated service.
Ethan Banks (00:00:00) – Automate your security framework compliance with sponsor Drata. Drata delivers continuous compliance no matter how fast your company is growing. Find out more at drata.com/partner/daytwocloud. That’s d r a t a dot com slash partner slash day two cloud.
Ned Bellavance (00:00:19) – Welcome to day two Cloud. Today’s topic is network automation, and we have two network automation experts who have thought hard about the problem as guests. We’ve got Chris Grundemann and Scott Robohn and they are part of the Network Automation Forum. What is the Network Automation Forum, Ethan?
Ethan Banks (00:00:36) – It is a group that is tr...

Today’s Day Two Cloud kicks off an occasional series on cloud essentials. For the first episode we discuss the Virtual Private Cloud, or VPC. A VPC is an fundamental construct of a public cloud. It’s essentially your slice of the shared cloud infrastructure, and you can launch and run other elements within a VPC to support your workload.

In this episode, Ned Bellavance walks through key components of the VPC including regions and availability zones, networking and IP addressing, paid add-ons, data egress and associated charges, monitoring and troubleshooting a VPC, and basic security controls.

Note that this conversation is AWS-centric. Azure, Google, and other public clouds also have VPC-like constructs, but with their own terminology and subtle differences. Rather than spend all of our time on comparisons, we use AWS as a baseline and will leave it to you to figure out the variations.

Sponsor: DoiT

An award-winning strategic partner of Google Cloud and AWS, DoiT works alongside more than 3,000 customers to save them time and money. Combining intelligent software with expert consultancy and unlimited support, DoiT delivers the true promise of the cloud at peak efficiency with ease, not cost. Their technology is backed by deep multicloud expertise in the analytics, optimization and governance of cloud architecture, as well as specializations in Kubernetes, AI, and more. Learn more at doit.com.

Show Links:

Amazon Virtual Private Cloud – AWS

Amazon VPC User Guide – AWS

Overview of Data Transfer Costs for Common Architectures – AWS

Transcript

Transcripts are automated and best-effort.

Ethan Banks (00:00:00) – Today’s podcast is sponsored by Do It Reduce Your Cloud spend by improving your cloud efficiency with Do It and award winning strat…

Full Transcription

Edit Speaker’s Names

Ethan Banks (00:00:00) – Today’s podcast is sponsored by Do It Reduce Your Cloud spend by improving your cloud efficiency with Do It and award winning strategic partner of Google Cloud and AWS. Find out more at Doit. That’s it. Dot com. Welcome to day two, Cloud. And today, Ned and I are going to begin a series of cloud essentials. What is Cloud Essentials, you might ask? Well, some of the fundamentals that you might want to know about if you are working in the cloud in today’s topic are vpcs. Because net, I don’t think it gets more essential than Vpcs.

Ned Bellavance (00:00:36) – They are a pretty foundational building block of pretty pretty much anything else you’re going to do when it comes to cloud computing, at least from an infrastructure perspective. So it’s probably a good place to start.

Ethan Banks (00:00:47) – Now, Vpcs. We’re going to be talking about them from an AWS centric perspective. If you look at Azure, if you look at GCP and a lot of the other public cloud providers that are out there, they may have slightly different terminology.

Ethan Banks (00:01:01) – But the conversation today that Ned and I are going to have is focused on the way...

Today on Day Two Cloud we dive into the implications of licensing changes that HashiCorp has made to its popular Terraform software. In short, the company has switched from an open source to a business source license. HashiCorp says it felt compelled to make the change to ensure that some other business entity doesn’t take the open-source software and turn it into a competing product (looking at you, AWS). Will the licensing change have a significant impact? For 99% of users probably not, but there are caveats and concerns to discuss.

This episode also covers some other items of note in the cloud world, including new technical projects, some cloud news, the collapse of NFT prices, and stupid AI tricks.

Today’s episode is a crossover with Chaos Lever, a weekly podcast co-hosted by Ned Bellavance and Chris Hayner that covers IT news.

Sponsor: DoiT

An award-winning strategic partner of Google Cloud and AWS, DoiT works alongside more than 3,000 customers to save them time and money. Combining intelligent software with expert consultancy and unlimited support, DoiT delivers the true promise of the cloud at peak efficiency with ease, not cost. Their technology is backed by deep multicloud expertise in the analytics, optimization and governance of cloud architecture, as well as specializations in Kubernetes, AI, and more. Learn more at doit.com.

Show Links:

Chris Hayner on LinkedIn

Chaos Lever Podcast

Terraform is dead; Long live Pulumi? – Mat Duggan

The OpenTF Manifesto

HashiCorp’s Licensing Change is only the Latest Challenge to Open Source – The New Stack

Jetporch – Substack

Ubicloud – GitHub

GCP offering 200Gb free egress on their Standard Tier – YCombinator

SUSE to be taken private by its majority shareholder – Silicon Angle

‘Bored Apes’ investors sue Sotheby’s, Paris Hilton and others as NFT prices collapse – CNN

What happens when thousands of hackers try to break AI chatbots – NPR

Driverless Cars Get Stuck In Wet Concrete In San Francisco – NY Times

a href="https://www.theatlantic.

Today on Day Two Cloud we serve up a bowl of acronym soup: SSE, SASE, and SD-WAN. SSE (Secure Service Edge) and SASE (Secure Access Service Edge) are Gartner terms for cloud-delivered security services including firewalls, IDS/IPS, secure Web gateways, cloud access security brokers, and others. The general difference between the two is that SASE tends to incorporate SD-WAN, which provides the network access to the cloud services. With SSE, you have to bring your own connections.

On today’s show we’ll examine the similarities and differences in these offerings, the drivers for cloud-delivered security, the role of networking in delivering these services, where and how zero trust can come into play, some of the big players in these spaces, and more.

Our guest is Tom Hollingsworth, analyst at Gestalt IT.

Show Links:

Gestalt IT

Tech Field Day

Become a Tech Field Day delegate

NetworkingNerd.net

Zero Trust Architecture – NIST

Tomversations: SSE vs. SASE – YouTube

Red teams attack a customer’s security systems. The idea of a red team, whether as consultants or in-house, is to approach the target like an attacker would. A red team includes technical and human-based exploit and attempts to test defenses, probe for weaknesses, and identify vulnerable systems and processes.

While red teaming is similar to a penetration test, a penetration test tends to limit its scope to a single technology or application and report on all vulnerabilities uncovered. A red team exercise includes the whole organization and seeks to achieve a specific objective like an attacker would–for example, exfiltrate data, install malware, or steal money.

Our guest and guide to red teaming and how to get the most out of the exercise is Gemma Moore, Director at Cyberis.

We discuss:



* What red teams do

* Why a company might hire a red team

* How red teams differ from penetration testing

* Pitting red teams against blue teams

* Getting useful outcomes from a red team exercise

* Red team legal and ethical boundaries

* Red teaming cloud vs. on-prem infrastructure

* Limitations of red teaming

* Yellow teams, purple teams, and orange teams

* More



Takeaways:



Red teaming can provide effective and realistic ways of assessing the capability of detection and response teams so that gaps in controls and coverage can be identified and addressed

Legal and ethical considerations mean an ethical red team can’t necessarily directly do everything an adversary would do – but working with a red team can allow events to be simulated to assess the impact in a controlled way

For any given organization or budget where a red team is needed to challenge security controls, there is likely to be a variant of red teaming that can be used to help highlight gaps. Typically, the compromise is between lower realism and lower budgets vs. higher realism and higher budgets.



Show Links:

Gemma Moore on LinkedIn

Cyberis Blog

Try Hack Me

Hack The Box

PEN-200: Penetration Testing with Kali Linux – OffSec

Offensive Cyber Security Training – Zero Point Security

Crest

US SANS