https://github.com/sysdiglabs/terraform-azurerm-secure
https://github.com/sysdiglabs/terraform-azurerm-secure
Last synced: 6 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/sysdiglabs/terraform-azurerm-secure
- Owner: sysdiglabs
- License: apache-2.0
- Created: 2023-08-16T19:21:16.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-25T06:02:33.000Z (over 1 year ago)
- Last Synced: 2024-10-25T09:37:07.304Z (over 1 year ago)
- Language: HCL
- Size: 191 KB
- Stars: 0
- Watchers: 7
- Forks: 4
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.txt
- Codeowners: CODEOWNERS
- Authors: AUTHORS
Awesome Lists containing this project
README
# Sysdig Secure for Cloud in Azure
Terraform module that deploys the Sysdig Secure for Cloud stack in Azure.
With Modular Onboarding, introducing the following design and install structure for `terraform-azurerm-secure`:
* **[Onboarding]**: It onboards an Azure subscription or Tenant for the first time to Sysdig Secure for Cloud, and collects
inventory and organizational hierarchy in the given tenant. Managed through `onboarding` module.
Provides unified threat-detection, compliance, forensics and analysis through these major components:
* **[CSPM](https://docs.sysdig.com/en/docs/sysdig-secure/posture/)**: It evaluates periodically your cloud configuration, using Cloud Custodian, against some benchmarks and returns the results and remediation you need to fix. Managed through `config-posture` module.
* **[CDR (Cloud Detection and Response)](https://docs.sysdig.com/en/docs/sysdig-secure/threats/activity/events-feed/)**: It sends periodically activity logs to Sysdig by directing those to a dedicated Event Hub which will be queried by the Sysdig backend to retrieve the data for log ingestion. Enabled via `event-hub` integrations module.
* **[Vulnerability Management Agentless Host Scanning](https://docs.sysdig.com/en/docs/sysdig-secure/vulnerabilities/)**: It uses disk snapshots to provide highly accurate views of vulnerability risk, access to public exploits, and risk management. Managed through `agentless-scanning` module.
For other Cloud providers check: [AWS](https://github.com/draios/terraform-aws-secure-for-cloud) , [GCP](https://github.com/draios/terraform-google-secure-for-cloud)
## Modules
### Feature modules
These are independent feature modules which deploy and manage all the required Cloud resources and Sysdig resources
for the respective Sysdig features. They manage both, onboarding a single Azure Subscription or an Azure Tenant to Sysdig Secure for Cloud.
`onboarding`, `config-posture` and `agentless-scanning` are independent feature modules.
A Service Principal is created per each independent module due to permission scoping, if you want to use a pre-existing one instead of creating a new one, refer to each module's README file.
### Integrations
The modules under `integrations` are feature agnostic modules which deploy and manage all the required Cloud resources and Sysdig resources
for shared Sysdig integrations. That is to say, one or more Sysdig features can be enabled by installing an integration.
These modules manage both, onboarding a single Azure Subscription or an Azure Tenant to Sysdig Secure for Cloud.
`event-hub` is an integration module.
A Service Principal is created per each independent integration module due to permission scoping, if you want to use a pre-existing one instead of creating a new one, refer to each module's README file.
## Examples and usage
The modules in this repository can be installed on a single Azure subscription, or on an entire Azure Tenant, or management groups within the Tenant.
The `test` directory has sample `examples` for all these module deployments i.e under `single_subscription`, or `organization` sub-folders.
For example, to onboard a single Azure subscription, with CSPM enabled, with modular installation :-
1. Run the terraform snippet under `test/examples/modular_single_subscription/onboarding_with_posture.tf` with
the appropriate attribute values populated.
2. This will install the `onboarding` module, which will also create a Cloud Account on Sysdig side.
3. It will also install the `config-posture` module, which will also install cloud resources as well as Sysdig resources
for successfully running CSPM scans.
4. On Sysdig side, you will be able to see the Cloud account onboarded with required components, and CSPM feature installed and enabled.
## Best practices
For contributing to existing modules or adding new modules, below are some of the best practices recommended :-
* Module names referred and used in deployment snippets should be consistent with those in their source path.
* A module can fall into one of two categories - feature module or an integrations module.
* Every user-facing deployment snippet will,
- at the top level first call the feature module or integrations module from this repo. These modules deploy corresponding cloud resources and Sysdig component resources.
- the corresponding feature resource will be added as the last block and enabled from the module installed component resource reference.
See sample deployment snippets in `test/examples` for more.
* integrations modules are shared and could enable multiple features. Hence, one should be careful with changes to them.
* Module naming follows the pattern with "-" , resource and variable naming follows the pattern with "_".
## Authors
Module is maintained and supported by [Sysdig](https://sysdig.com).
## License
Apache 2 Licensed. See LICENSE for full details.