Scenarios, Custom PGO User and more

0.4.1 (2024-07-18)

Changes

• AWS ECS configurations are now split into two separate configurations ecs-ec2 and ecs-fg. This simplifies the deployment and now works the same way as AWS EKS.
• All Terraform Modules and Providers are now version fixed.
• Improved Naming of instances in regards to the PGO Active Directory
• pgo --config does now allow to disable initialization of Terraform after a first run. This speeds up configuration changes dramatically.
• Playground One can optionally use its own AWS user with limited privileges. The user can be created by running pgo --apply user, which of course requires administrative privileges with your own AWS user. You have to enable the PGO user in the configuration, but you can disable it at any time.
• Migrated EKS cluster deployments to use the Vision One Terraform Provider.
• There are new scenarios available:
  • Deploy Service Gateway on AWS manually
  • Deploy Service Gateway on AWS automatically
  • Integrate an Active Directory via Service Gateway on AWS
• New Scenario section: Workflow and Automation - Third-Party Integration:
  • Setup Splunk
  • Integrate Splunk with Vision One XDR
  • Integrate V1CS Customer Runtime Security Rules with Splunk
  • Setup Elastic Stack
  • Integrate Elastic Stack with Vision One
• XDR Threat Investigation: CloudTrail
• Identity Posture: Populate the Active Directory