Skip to content
Scale To Zero by Cloudanix
TA

Guest

Tom Adamski

](https://www.

Episode with Tom

What Tom covered

Network Security Fortress: Master Network Segmentation with Tom Adamski

Tom Adamski recommends performing a risk assessment of the business and infrastructure before designing network segmentation — let the drivers (compliance, security, or management) shape the approach. Segmentation should stay at a broader level to remain operable; overly granular rules become difficult to maintain. AWS security tools like security groups, NACLs, subnets, and firewalls are additive, not interchangeable.

  • ​​Before working on NS, Perform Risk Assessment of the business & infrastructure. Depending on the need like compliance or security or management or others, build your Network Segmentation.
  • Network Segmentation should be performed more at a broader level instead of very granular. This would become difficult to operate and maintain.
  • Security tools are AND and not OR in AWS. Depending on the use cases, leverage the security tools and appliances like Security Groups, NACLs, Subnets, Transit Gateways, Firewalls, etc.

New episodes twice a month

No security question left unanswered.

Follow Scale To Zero wherever you listen, or send us the question your team is stuck on and we will put it to an expert.