Since releasing SecureX orchestration, we’ve frequently printed two forms of content material for our clients to import and use: atomic actions and workflows. Atomic actions are small, re-usable features that permit you to do easy issues like isolating an endpoint in Cisco Safe Endpoint. Workflows are extra advanced combos of actions, usually made up of a number of atomic actions, that accomplish a broader goal. One in every of our hottest workflows fetches weblog posts from Talos after which conducts an investigation into every publish utilizing a buyer’s SecureX-integrated merchandise. As of this weblog publish’s publishing, we’ve launched 75 workflows. So, let’s speak about what’s new…
Previously, whenever you wished to speak with SecureX APIs, you needed to undergo a multi-step course of to generate an API consumer, use that API consumer to get a token, after which refresh the token each 10 minutes. This course of wasn’t precisely easy, so in April we launched the brand new SecureX Token account key. This particular sort of account key means that you can combine with SecureX APIs with out creating an API consumer, producing a token, or worrying about when the token expires. Merely use a SecureX goal together with a SecureX Token account key and the platform takes care of the tokens. For extra details about this replace and the right way to benefit from this new performance, take a look at our documentation. Take into account that in case your orchestration tenant was created previous to April 2022, you could must create a SecureX Token.
Now that we’ve SecureX Token account keys and clients have been utilizing them for just a few months, we determined it was time to replace all of our beforehand printed workflows to be absolutely suitable with the brand new account key sort. All 24 workflows utilizing SecureX APIs have now been up to date to leverage SecureX Tokens. For extra details about Cisco-published workflows, take a look at our workflow listing.
Cisco Safe Firewall + SecureX Orchestration
Since Cisco Safe Firewall is sort of all the time deployed on-premises and behind a firewall, integrating it with SecureX orchestration within the cloud has required the usage of a SecureX orchestration distant. Not all of our clients are focused on deploying an on-premises digital machine or they lack a VMware ESXi deployment inside which to run the VM. Now, with the discharge of the SecureX Safety Providers Change (SSE) API proxy, you may combine your SSE-registered FMC gadgets with orchestration workflows with out the necessity for extra remotes or digital machines. To point out how this works and spotlight how simple this integration is, we re-released 5 of our current FMC workflows with help for the SSE API proxy:
To remain up to date on what’s new with SecureX, take a look at the next sources:
We’d love to listen to what you assume. Ask a Query, Remark Under, and Keep Linked with Cisco Safe on social!
Cisco Safe Social Channels