Reducing Friction within SecureX Orchestration

 <div>          <img src="https://www.infracom.com.sg/wp-content/uploads/2022/11/cover-photo.png" class="ff-og-image-inserted" />          </div>     

Since releasing SecureX orchestration, we’ve regularly published two forms of content for our clients to import and use: atomic activities and workflows. Atomic activities are small, re-usable features that enable you to do basic things such as isolating an endpoint in Cisco Protected Endpoint. Workflows tend to be more complicated combinations of activities, comprised of multiple atomic activities often, that accomplish a broader objective. Among our hottest workflows fetches blogs from Talos and conducts a study into each post utilizing a customer’s SecureX-integrated items. As of this blog page post’s publishing, we’ve launched 75 workflows. Therefore, let’s discuss what’s new…

 <h2>          <span>     SecureX Tokens     </span>          </h2>     

In the past, once you wanted to talk to SecureX APIs, you’d to undergo a multi-step approach to create an API client, use that API client to obtain a token, and refresh the token every ten minutes then. This technique wasn’t exactly simple, therefore in April we launched the brand new SecureX Token account crucial . This special kind of account key enables you to integrate with SecureX APIs without generating an API client, producing a token, or fretting about once the token expires. Basically work with a SecureX focus on together with a SecureX Token accounts key and the system manages the tokens. To find out more concerning this update and how exactly to benefit from this new functionality, have a look at our documentation . April 2022 remember that if your orchestration tenant was made prior to, you might need to produce a SecureX Token.

Now that we’ve SecureX Token account clients and keys have already been using them for a couple months, we decided it had been time to update our earlier published workflows to end up being fully compatible with the brand new account key kind. All 24 workflows using SecureX APIs have already been updated to leverage SecureX Tokens now. To learn more about Cisco-published workflows, have a look at our workflow list .

 <h2>          <span>     Cisco Safe Firewall + SecureX Orchestration     </span>          </h2>     

Since Cisco Secure Firewall is definitely deployed on-premises and behind a firewall almost, integrating it with SecureX orchestration in the cloud has required the usage of a SecureX orchestration remote control . Not absolutely all of our clients want in deploying an on-premises virtual device or they absence a VMware ESXi deployment within which to perform the VM. Today, with the discharge of the SecureX Safety Services Swap (SSE) API proxy , it is possible to integrate your SSE-authorized FMC gadgets with orchestration workflows with no need for extra remotes or virtual devices. Showing how this ongoing functions and highlight how simple this integration is, we re-launched five of our present FMC workflows with assistance for the SSE API proxy:

 <h2>          <span>     Assets     </span>          </h2>     

To remain updated on what’s fresh with SecureX, browse the following resources:

 <hr />     

 <em>     We’d want to hear everything you think. Ask a relevant question, Comment Below, and Remain Linked to Cisco Secure on sociable!     </em>     

 <strong>     Cisco Protected Social Channels     </strong>     

 <strong>          <a href="https://www.instagram.com/CiscoSecure/" target="_blank" rel="noopener noreferrer">     Instagram     </a>          </strong>          <br />          <strong>          <a href="https://www.facebook.com/ciscosecure/" target="_blank" rel="noopener noreferrer">     Facebook     </a>          </strong>          <br />          <strong>          <a href="https://twitter.com/CiscoSecure" target="_blank" rel="noopener noreferrer">     Twitter     </a>          </strong>          <br />          <strong>          <a href="https://www.linkedin.com/showcase/cisco-secure" target="_blank" rel="noopener noreferrer">     LinkedIn     </a>          </strong>     

 <pre>          <code>        &lt;br&gt;