Heavy Networking 599: DriveNets Taps Disaggregation To Build Networks Like Cloud (Sponsored)
On today's sponsored Heavy Networking we talk with DriveNets about why it’s time to take the disaggregated model--where you buy whitebox hardware and put a network operating system of your choice on it--seriously. Along the way, we’re going to hit DriveNets network architectures and operating models, and get you thinking about why disaggregated networking might make sense for you.
The post Heavy Networking 599: DriveNets Taps Disaggregation To Build Networks Like Cloud (Sponsored) appeared first on Packet Pushers.
Heavy Networking 599: DriveNets Taps Disaggregation To Build Networks Like Cloud (Sponsored)
On today's sponsored Heavy Networking we talk with DriveNets about why it’s time to take the disaggregated model--where you buy whitebox hardware and put a network operating system of your choice on it--seriously. Along the way, we’re going to hit DriveNets network architectures and operating models, and get you thinking about why disaggregated networking might make sense for you.AWS Networking – Part VIII: AWS Network ACL (NACL)
In this section, I am going to introduce the default Network ACL for subnets in VPC NVKT-VPC-01.
Figure 1-28 shows the complete structure of our VPC NVKT-VPC-01. We have a Public subnet 10.10.0.0/24 in AZ eu-west-2c a Private subnet 10.10.1.0/24 in AZ eu-west-2a. Both subnets are protected by the default VPC’s NACL named NWKT-NACL. NACL allows all traffic to and from the subnet by default.
Figure 1-37: Complete VPC Stack.
Continue reading
Cloud Native Driving Change in Enterprise and Analytics
Software development via cloud-native resources continues to gain traction among enterprises looking for scale, security, and accessibility of business intelligence.AWS Networking – Part VII: Create Subnet and RT Using AWS CloudFormation
In this post, we create a Subnet with the set of properties and attach it to VPC. We also specify a Route Table, which we associate with the Subnet using association.
1) AWS::EC2::VPC (NwktVPC)
2) AWS::EC2::Subnet (NwktSubnet)
3) AWS::EC2::RouteTable (NwktPUB2RouteTable)
4) AWS::EC2::SubnetRouteTableAssociation(NwktRouteTableAssociation)
We are using a Ref function for defining the dependencies between AWS resources when the actual AWS resource Identifier is unknown. For example, the Ref function in AWS::EC2::Subnet resource [2] refers to the resource AWS::EC2::VPC’s logical name NwktVPC (A). We have to use an intrinsic function because we don’t know which VPC Identifier AWS generates to VPC. After creating the subnet, we specify the subnet-specific Route Table [3]. First, we need to bind it to VPC using the Ref function value NwktVPC (B). Next, we “glue” the Route Table to Subnet using RouteTableAssociation, where we use two Ref functions. The first one refers to Route Table (C), and the second to Subnet (D).
Figure 1-34: Subnet Route Table.
Continue reading
What does the Internet Society do and who are they? – Massimiliano “Max” Stucchi, Technical Advisor, European Bureau @ Internet Society
The Internet Society supports and promotes the development of the Internet as a global technical infrastructure, a resource to enrich people’s lives, and a force for good in society. Our work aligns with our goals for the Internet to be open, globally-connected, secure, and trustworthy
Worth Reading: Breaking Down Silos
Here’s another masterpiece by Charity Majors: Why I hate the phrase “breaking down silos”. A teaser in case you can’t decide whether to click the link:
When someone says they are “breaking down silos”, whether in an interview, a panel, or casual conversation, it tells me jack shit about what they actually did.
Enjoy ;)
Worth Reading: Breaking Down Silos
Here’s another masterpiece by Charity Majors: Why I hate the phrase “breaking down silos”. A teaser in case you can’t decide whether to click the link:
When someone says they are “breaking down silos”, whether in an interview, a panel, or casual conversation, it tells me jack shit about what they actually did.
Enjoy ;)
IPv6 Buzz 085: Is Your Network Ready For IPv6?
In this episode of IPv6 Buzz, we discuss IPv6 network readiness assessments, what they should include, and some helpful ideas for where to start.
The post IPv6 Buzz 085: Is Your Network Ready For IPv6? appeared first on Packet Pushers.
IPv6 Buzz 085: Is Your Network Ready For IPv6?
In this episode of IPv6 Buzz, we discuss IPv6 network readiness assessments, what they should include, and some helpful ideas for where to start.Augmented MISP Integration with NSX Advanced Threat Analyzer
Contributors: Jason Zhang (NSBU TAU), Stefano Ortolani (NSBU TAU)
Introduction
Formerly known as the Malware Information Sharing Platform, MISP is a leading open-source threat intelligence platform (TIP) that organizations of all sizes can leverage to store, share, and enrich threat indicators of compromise (IoCs).
The MISP ecosystem primarily comprises two parts: MISP core (or engine) and MISP modules. MISP core is responsible for the main functionality of the platform, while MISP modules were introduced to extend the capability of MISP without changing MISP core components.
Thanks to the simple API interface provided by MISP, many third-party MISP modules have been developed to greatly extend MISP’s capabilities. There are mainly three types of MISP modules: expansion modules, import modules, and export modules. More details on MISP modules can be found on MISP’s GitHub MISP module repository, which includes three modules developed by Lastline (now part of VMware) that integrate MISP with VMware NSX Advanced Threat Analyzer (ATA), as we reported earlier.
Recently VMware’s Threat Analysis Unit (TAU) developed a new expansion module, which replaces the three Lastline modules. The improvements from the new module are twofold: a simplified enrichment process and an augmented enrichment capability.
In this blog post, Continue reading