What's Happening?
Clavister has released a detailed guide for deploying its NetWall virtual firewall (cOS Core) within Amazon Web Services (AWS) using the AWS Command Line Interface (CLI). The process, estimated to take about 30 minutes with 10 minutes of waiting for image
import, involves several steps. Users will convert the cOS Core image, upload it to Amazon S3, import the file as a snapshot, and then create an Amazon Machine Image (AMI) from the snapshot. Following this, the firewall is started as an EC2 instance. The guide emphasizes logging in with the EC2 Serial Console to set the password and management access, ensuring security before the firewall is exposed to the internet. It also covers creating a security group that allows all traffic, with the firewall itself handling the filtering. The example deployment uses the `eu-north-1` (Stockholm) AWS region, an x86_64 cOS Core image, and an instance with 2 vCPU and 4 GB memory. The guide also provides instructions for securing management access by limiting it to a specific IP address and setting a default route for internet connectivity.
Why It's Important?
This deployment guide is important for U.S. businesses and organizations that rely on AWS for their cloud infrastructure and require robust network security. By providing clear, step-by-step instructions, Clavister enables these entities to integrate their NetWall virtual firewalls seamlessly into their AWS environments. This enhances the security posture of cloud-based applications and data, which is critical given the increasing sophistication of cyber threats. The ability to deploy and manage firewalls using the AWS CLI offers automation and scalability benefits, allowing organizations to quickly provision and configure security measures as their cloud footprint expands. Furthermore, the emphasis on securing management access and setting up proper routing ensures that the firewall itself is protected from unauthorized access, a fundamental aspect of overall cybersecurity. This guide supports the growing trend of cloud adoption by providing essential tools for maintaining secure and compliant operations within the AWS ecosystem.
What's Next?
After deploying the Clavister NetWall virtual firewall, users will need to install a license, as the cOS Core runs in demo mode for a limited time without one. The guide directs users to the cOS Core Administration Guide for adding IP policies, which are necessary for the firewall to begin forwarding traffic effectively. For those requiring a consistent public IP address, the guide suggests using an Elastic IP, which incurs charges while active. Users whose own IP addresses change will need to reconfigure management access via the serial console. Additionally, the guide touches upon routing traffic for other servers through the firewall, which requires further configuration, including potentially turning off AWS source and destination checks on the firewall. Clavister also provides instructions for removing all deployed resources, which is useful for testing or decommissioning environments. Future developments may include updated guides for newer AWS regions, instance types, or cOS Core versions, as well as integrations with other AWS security services.
Beyond the Headlines
The detailed deployment process outlined by Clavister highlights the increasing complexity and specialization required for cloud security. While cloud providers like AWS offer foundational security features, the responsibility for securing applications and data often falls to the customer. This guide underscores the 'shared responsibility model' in cloud computing, where AWS secures the underlying infrastructure, and the customer is responsible for security in the cloud. The use of the AWS CLI for deployment signifies a move towards Infrastructure as Code (IaC) practices, promoting automation, consistency, and repeatability in security deployments. This approach can reduce human error and improve compliance. The guide's focus on granular control over management access and traffic filtering reflects the need for fine-grained security policies in dynamic cloud environments. This level of control is crucial for organizations dealing with sensitive data or operating under strict regulatory requirements, as it allows them to tailor their security posture precisely to their operational needs and risk profiles.
