From the course: DevSecOps in Action: Securing and Governing Multicloud Infrastructures

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Dynamically test internal deployments

Dynamically test internal deployments

- [Instructor] Single cloud dynamic application security testing or DAST, takes place within a private network after a deployment to a pre-production environment is complete. This can be set up by either setting up the DAST Scanner in the pre-production network or by setting up the CI/CD runner to run in the pre-production network. When running deployments across multiple clouds, this approach becomes more challenging to implement. This is where remote access solutions come in and ease the complexity. Using Twingate, a GitHub Actions service account can be created and granted access to a frontend in AWS and a backend in Azure. This will enable GitHub Actions to easily hit the API endpoints internally, regardless of what cloud they're in. DAST can then take place within the private network. To start, open the Twingate dashboard and navigate to Team Services and Create a New Service Account. Name the service account GitHub…

Contents