Hello Cisco Community! Cisco Secure is moving forward with Cisco hosted SecureX Integration Modules, where no serverless relay or docker container is needed any more. To switch to the Cisco hosted version of your SecureX Integration Module, just follow these easy steps.
Relays for Cisco SecureX 3rd Party Modules enable communication between Cisco SecureX and 3rd Party vendors. The Serverless Template uses AWS as an example, that is very inexpensive and easy to deploy: https://github.com/CiscoSecurity/tr-05-serverless-relay
This Guide is separated into 3 parts
Part 1&2 just need to be done once.
Which Modules are possible today?
|To install, configure and maintain the Serverless Relay, which is an App hosted by Amazon, we need some components. Enclosed a short description what is needed. This is an overview. The page will guide you step-by-step through the necessary steps to make your Serverless Relay up and running.|
After you configured the Configuration of the WebApp locally on your endpoint, there is a simple command to upload or update your WebApp on AWS.
During the configuration of the Module (AWS WebApp) locally on your endpoint, all needed Authentication Tokens and URLs are generated, which are used to configure your 3rd Party Module in SecureX.
Why we need the AWS environment? After your module is configured, just start an investigation. The UI shows which Modules have been queried.
In this section we will Guide you to prepare an AWS environment used to provide the virtual apps for your SecureX Modules. We will do just a few steps.
Note, this Step-by-Step Guide shows how to generate an AWS Account for Serverless Applications. Keep in mind, if you have already other components configured in AWS, your Screen may look like a little bit different than the screenshots shown in this guide.
The next Steps will guide you through the implementation of the AWS environment, which acts as a "Service Proxy" between Cisco SecureX/CTR Modules and 3rd Party Modules.
Benefit of this approach are: