
Overview
Hyper Scale Security for your Hyper Scalable Clouds Whether your data and applications are stored on premises, in the data center, or public clouds (or a combination of all three), organizations still need to meet their requirements of security, control, compliance, and governance by themselves. The on-demand nature of public clouds such as AWS naturally means that workloads move and regroup, where maintaining continuous visibility and control over the rapid changes calls for expert intervention. Common security challenges include: Centralized visibility and threat management for your hybrid environment Deploy applications and workloads securely Manage access & control privileges to cloud and on-premises workloads Secure data transfer, data migrations Accomplish all of the security deployments at the pace and scale demanded by cloud architectures
Highlights
- FireMon can easily create, maintain, and distribute policies in highly dynamic networks, as well as scope the impact of proposed changes to your security. By automating & orchestrating, Security Manager ensures your ability to operate at scale across cloud, virtual and hybrid environments.
- Through traffic flow analysis, FireMon tracks behavior across your network to identify which applications are being used. You can correlate vulnerability scans with access path analysis to trace every available path across the network to reduce your attack surface with a defined remediation.
- Automated compliance assessments help you validate your configuration requirements and alert you to violations. Security Manager out-of-the-box audit ready and customizable reports saves time and gives you the confidence to meet your regulatory and internal security demands.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
Please see seller website for refund details.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
Before launch, in the AMI configuration settings, you must add additional volume to prevent launch failure.
Add Storage tab, click Add New Volume and in the Size field enter at least 600. Do not change the Root Volume Type.
Complete FMOS Initial Setup after launch:
- Open a web browser.
- Navigate to https://<hostname>:55555/setup, replacing <hostname> of the SIP instance running in AWS with the IP or the hostname.
- In the Authentication dialog box-Username is fmosadmin- Password is the EC2 Instance ID- Click Submit
- After authenticating, complete the required fields in the FMOS Initial Setup form. The username is read-only and cannot be changed, but you can update the password.
- After submitting the FMOS Initial Setup form, FMOS will begin the deployment process.Log in to SIP after deployment:
- Open a web browser tab.
- Enter the IP address of your SIP/AWS instance.
- Enter your username and password.
- Username is firemon (case-sensitive)
- Password is the MAC address for the instance
- Click Log in. For details, see: https://www.firemon.com/wp-content/uploads/AWS-AMI-Launch-and-FMOS-Install.pdf
CF template Usage Instruction: 1.Go to AWS marketplace subscription and Launch cloud formation teamplate. 2.Choose Action 'Launch Cloud formation' and click on Launch 3.Enter Stack Name. 4.Enter all mandatory fields in Parameters. VPC ID Subnet ID Instance Type Key Pair Name IP address Volume Size FMOS username 5.Specify Ecosystem in "Machine Configuration". 6.Add Organization Name. 7.Click Next. 8.Review: Review all sections entered and click Next. 9.A new stack with above Stack Name is created with status "CREATE_COMPLETE". 10.Go to EC2 Dashboard, a new instance is created. 11.After the deployment process completes, you can log in to Security Intelligence Platform to continue setting up your network, such as adding users and devices. a. Open another browser tab. b. Enter the IP address of your AWS instance, For example, https://<hostname_or_IPaddress>;. c. Enter your username and password: Username is firemon (case-sensitive) Password is the MAC address for the instance with colons removed and lowercase letters instead of uppercase letters. For example, a MAC address of 00:05:95:A1:2B:CC would be 000595a12bcc. This is a one-time password to use at first installation and will need to be reset after initial login. Click Log In
Resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products



Customer reviews
Great for Auditing Firewall Policies and Catching Redundant Rules
Powerful Centralized Policy Management, but Usability and Workflow Need Streamlining
Excellent Firewall Review Rules, Best Practices, and Compliance Support
Simplifies Rule Analysis and Compliance Reporting
Visibility has transformed daily security operations and simplifies multi-vendor policy changes
What is our primary use case?
My main use case for FireMon Security Manager is bringing visibility throughout the heterogeneous environment that I manage, enabled by the flexibility of the licenses and compatibility with a variety of vendors, including Cisco, Palo Alto, Fortinet, Huawei, and cloud and VMware environments.
The visibility I gained with FireMon Security Manager became evident when we needed to change our firewall vendors from Cisco to Fortinet, allowing us to perform reusable checks on the rules across all devices while transitioning smoothly to the new vendor.
FireMon Security Manager helped us further by providing visibility on changes made outside of our scheduled change windows, integrating with an ITSM solution via API to track changes initiated through tickets and ensuring compliance with our internal protocols.
What is most valuable?
The best features that FireMon Security Manager offers include license flexibility, vendor compatibility, real-time information, and change checks, which enhances my day-to-day work by consolidating my entire environment into a single pane of glass.
The visibility, topology, compliance, vulnerability management, and daily filters provided by FireMon Security Manager have made our daily operations much easier, significantly saving us time and enhancing our security practices.
I can add that we can integrate FireMon Security Manager via API with almost any solution, and its add-on, FireMon Insights, allows for the creation of diverse KPIs and dashboards tailored to our environment's needs.
Since adding FireMon Security Manager inside our environment, our security perspective improves daily, giving us visibility on every change made and allowing us to address any potential security vulnerabilities timely.
What needs improvement?
I think FireMon Security Manager could improve with a SaaS delivery model for easier connectivity and perhaps provide more regular updates and flexible dashboard options for better usability.
I believe the solution is straightforward, and while it includes many integrations, additional technical information on its internal workings would allow for more flexibility and deeper integrations with our environment.
For how long have I used the solution?
I have been working with FireMon Security Manager for the past ten years, as it is the second solution that I started working with here at AtivaSec.
Which solution did I use previously and why did I switch?
I previously used AlgoSec and Tufin, switching from AlgoSec to Tufin, and when Tufin lost support in Brazil, I transitioned to FireMon Security Manager, which has proven to be a much better option.
Which other solutions did I evaluate?
I did not evaluate other options before choosing FireMon Security Manager, as I had worked with other solutions and found FireMon Security Manager's compatibility with multiple vendors to be a significant differentiator.
What other advice do I have?
My advice for those considering FireMon Security Manager is to conduct a POC, share your use cases with the FireMon Security Manager salesperson, and utilize the available templates for assessments.
I have shared everything about FireMon Security Manager, and I think it is a great solution. I have given this review a rating of ten out of ten.