API Access Lets Security Engineers Get Creative

API Access Lets Security Engineers Get Creative 

Having out-of-the-box integrations with common tools and cloud platforms are critical enablers to securitybut flexibility is important too. Most enterprises have multiple vendors across their infrastructure and want access to an open API so they build their own integrations. 

FireMon recently announced a set of integrations for Microsoft Azure, CISCO ACI, ServiceNow and Swimlane because we know many customers want to connect to these popular platforms. These integrations enable them to properly and adequately configure security for these cloud platforms in alignment with global policies being applied in their on-premise environment. It also enables them to see everything through a single user interface, so they have a complete picture on in place. 

We also know from our experiences internally there’s value in giving security professionals direct access to our API without a UI so they can plug FireMon into different parts of their environment how the want to 

Speed up security with scripting 

FireMon’s out-the-box integration speeds up security without being a barrier to the needs of lines of businessbut custom scripting is also taking off because it allows security engineers to do more customized connections on the fly 

By giving them access to the exact same API we use to build our solutions and integrate them with common tools and platforms, security engineers can make the same API calls FireMon does to do multiple things across their infrastructure. A common example is using the API to understand what people across the environment are doing and how existing rules have been applied. Security engineers can quickly discover how a rule is being used, when it was last used, and if the rule is still relevant. Having easy access to this information enables them to make quick, informed decisions about keeping or discarding rules, and remove bloat. 

API access brings knowledge access, which helps security engineers to build better, more streamlined integrations in their multi-vendor environments.  

Enabling automation with API access 

Getting the access and visibility they need to clean up rules means enterprises can take the next step of automating with confidence. 

Any automation must align withsecurity compliance framework, as well as specific industry standards such as PCI. Not only does access to the API enable security engineers to automate rules with the confidence they will work properlybut they can also be certain they won’t break compliance. API access lets them test their automation before it’s applied so they can get immediate feedback and understand the consequences of applying any new, automated rules and policies 

Complete visibility requires the flexibility of an open API 

A user-friendly User Interface (UI) is great for lines of business because it enables them to contribute to security hygiene and see how the applications and services that they spin up fit into the bigger picture. 

But for security engineers tasked with keeping compliant across a dispersed infrastructure populated by many different vendors, being able to build their own customized picture of what’s going on is critical. Getting full access to the FireMon API gives them the level of visibility they need so they can understand where compliance is broken, or if shadow rules are being run. Most of all, it allows security engineers to get creative when solving problems in a multi-vendor environment. As much as security is about robust policy and process, the complex nature of rapidly scaling cloud environments sometimes requires some imagination when solving unique integration challenges.  

By providing complete access to our open API, FireMon enables customers to stretch the capabilities of our product and derive even more value from it by being able to respond agilely to their own business-driven requirements.   

The post API Access Lets Security Engineers Get Creative appeared first on FireMon.

*** This is a Security Bloggers Network syndicated blog from FireMon authored by FireMon. Read the original post at: