Skip to content

Commit 77f6407

Browse files
author
iru
authored
Update _questionnaire.md
1 parent 7554716 commit 77f6407

File tree

1 file changed

+20
-13
lines changed

1 file changed

+20
-13
lines changed

use-cases/_questionnaire.md

Lines changed: 20 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
# Use-Case Questionnaire
22

3-
This questionnaire is aimed to help you/us find the most suitable example or self-baked use-case.
3+
This questionnaire is aimed to help you/us find the most suitable way of deploying [Sysdig Secure for Cloud](https://docs.sysdig.com/en/docs/installation/sysdig-secure-for-cloud/).
4+
45
Despite wanting only to trial it, we suggest that you deploy, and test it, in the most-similar situation to what
56
you have on your production environment.
67

@@ -10,18 +11,15 @@ Contact us with these questions answered to help us.
1011
> Sysdig Secure for Cloud is served in Terraform [AWS](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud), [GCP](https://github.com/sysdiglabs/terraform-google-secure-for-cloud) and [Azure](https://github.com/sysdiglabs/terraform-azurerm-secure-for-cloud)
1112
modules, and we also offer [AWS Cloudformation templates](https://github.com/sysdiglabs/aws-templates-secure-for-cloud)
1213

14+
<br/><br/>
1315

14-
## Client Infrastructure and Sysdig Features
16+
## Client Infrastructure
1517

1618
- does your company work under an organization (AWS/GCP) or tenant (Azure)?
1719
- if so, how many member accounts (aws) /projects (gcp) /subscriptions (azure) does it have?
18-
19-
- in what Sysdig features are you interested in?
20-
- [Runtime Threat Detection](https://docs.sysdig.com/en/docs/sysdig-secure/insights/)
21-
- [Compliance](https://docs.sysdig.com/en/docs/sysdig-secure/posture/compliance/compliance-unified-/) (cis benchmarks and others)
22-
- [Identity and Access Management](https://docs.sysdig.com/en/docs/sysdig-secure/posture/permissions-and-entitlements/)
23-
- Registry/repository [Image scanning](https://docs.sysdig.com/en/docs/sysdig-secure/scanning/)
24-
- Runtime workload image scanning (ecs on Aws, cloudrun on GCP, or container instances on Azure)
20+
- deployment type
21+
- are you familiar with the installation stack? Terraform or Cloudformation?
22+
- if you want to use Kubernetes workload for Sysdig deployment, what's your current way of deploying helm charts?
2523

2624

2725
### AWS
@@ -33,12 +31,21 @@ modules, and we also offer [AWS Cloudformation templates](https://github.com/sys
3331
- in case of ECS or K8S, do you have an existing cluster you would like to re-use?
3432

3533

36-
## Demo vs. Production
34+
## Sysdig Features
35+
36+
In what [Sysdig For Cloud Features](https://docs.sysdig.com/en/docs/sysdig-secure/sysdig-secure-for-cloud/) are you interested in?
37+
38+
- [Runtime Threat Detection](https://docs.sysdig.com/en/docs/sysdig-secure/insights/)
39+
- [Compliance](https://docs.sysdig.com/en/docs/sysdig-secure/posture/compliance/compliance-unified-/) (cis benchmarks and others)
40+
- [Identity and Access Management](https://docs.sysdig.com/en/docs/sysdig-secure/posture/permissions-and-entitlements/)
41+
- Scanning
42+
- Push-based registry/repository image scanning
43+
- Runtime workload image scanning (ecs on Aws, cloudrun on GCP, or container instances on Azure)
44+
- Note: Sysdig offers many other ways of performing scanning, and we recommend you to [Check all Scanning options in the Vulnerability Management](https://docs.sysdig.com/en/docs/sysdig-secure/vulnerabilities/)
45+
3746

38-
- Are you familiar with the installation stack? Terraform or Cloudformation.
39-
- We recommend that whether you are demoing or not, to go for the most production similar environment.
4047

41-
## Terraform Example Selection
48+
## Example Selection
4249

4350
| | Single | Organizational |
4451
| --| -- | -- |

0 commit comments

Comments
 (0)