Since releasing SecureX orchestration, we’ve frequently revealed two kinds of content material for our clients to import and use: atomic actions and workflows. Atomic actions are small, re-usable capabilities that assist you to do easy issues like isolating an endpoint in Cisco Secure Endpoint. Workflows are extra complicated mixtures of actions, typically made up of a number of atomic actions, that accomplish a broader goal. One of our hottest workflows fetches weblog posts from Talos after which conducts an investigation into every submit utilizing a buyer’s SecureX-integrated merchandise. As of this weblog submit’s publishing, we’ve launched 75 workflows. So, let’s speak about what’s new…
SecureX Tokens
In the previous, once you needed to speak with SecureX APIs, you needed to undergo a multi-step course of to generate an API shopper, use that API shopper 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 kind of account key lets you combine with SecureX APIs with out creating an API shopper, producing a token, or worrying about when the token expires. Simply use a SecureX goal along with a SecureX Token account key and the platform takes care of the tokens. For extra details about this replace and methods to reap the benefits of this new performance, try our documentation. Keep in thoughts that in case your orchestration tenant was created previous to April 2022, chances are you’ll must create a SecureX Token.
Now that we’ve got SecureX Token account keys and clients have been utilizing them for a couple of months, we determined it was time to replace all of our beforehand revealed workflows to be absolutely suitable with the brand new account key kind. All 24 workflows utilizing SecureX APIs have now been up to date to leverage SecureX Tokens. For extra details about Cisco-published workflows, try our workflow record.
Cisco Secure Firewall + SecureX Orchestration
Since Cisco Secure Firewall is nearly at all times deployed on-premises and behind a firewall, integrating it with SecureX orchestration within the cloud has required using a SecureX orchestration distant. Not all of our clients are involved in 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 Security Services Exchange (SSE) API proxy, you may combine your SSE-registered FMC units with orchestration workflows with out the necessity for extra remotes or digital machines. To present how this works and spotlight how simple this integration is, we re-released 5 of our present FMC workflows with assist for the SSE API proxy:
Resources
To keep up to date on what’s new with SecureX, try the next sources:
We’d love to listen to what you assume. Ask a Question, Comment Below, and Stay Connected with Cisco Secure on social!
Cisco Secure Social Channels
Instagram
Facebook
Twitter
LinkedIn
Share: