doc: update questionnaire

Author: iru

use-cases/_questionnaire.md

@@ -2,16 +2,18 @@
 
 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/).
 
-Despite wanting only to trial it, we suggest that you deploy, and test it, in the most-similar situation to what
-you have on your production environment.
+Despite wanting only to trial it, we suggest that you deploy, and test it, in th **most-similar situation to what
+you have on your production environment**.
 
 We are aware that current examples don't suit all situations, and we will keep improving them to be as configurable as possible.
 Contact us with these questions answered to help us.
 
-> 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)
+<br/>
+
+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)
 modules, and we also offer [AWS Cloudformation templates](https://github.com/sysdiglabs/aws-templates-secure-for-cloud)
 
-<br/><br/>
+<br/>
 
 ## Client Infrastructure
 
@@ -23,11 +25,13 @@ modules, and we also offer [AWS Cloudformation templates](https://github.com/sys
     - is it an organizational cloudtrail?
     - does the cloudtrail report to an SNS? if no, could you enable it?
     - if it's not organizational, does each trail report to the same s3 bucket?
-- how do you handle IAM permissions? any restriction we may be aware of? do you want us to set them up for you or would you just require a guidance and you will set them yourself?
-- deployment type
-  - are you familiar with the installation stack? Terraform, Cloudformation, AWS CDK, ...?
+- how do you handle **IAM permissions**? would you let our Terraform scripts set them up for you, or you want to set them yourself manually? any restriction we may be aware of?
+- how do you handle **outbound newtwork connection** securization? does your infrastructure have any customized VPC/firewally setup?
+- **Deployment** type
+  - are you familiar with the installation stack? Terraform, Cloudformation, AWS CDK, ...? Do you use any other InfraAsCode frameworks?
   - if you want to use Kubernetes compute for Sysdig deployment, what's your current way of deploying helm charts?
 
+<br/>
 
 ## Sysdig Features
 
@@ -39,7 +43,7 @@ In what [Sysdig For Cloud Features](https://docs.sysdig.com/en/docs/sysdig-secur
 - Scanning
   - Push-based registry/repository image scanning
   - Runtime workload image scanning (ecs on Aws, cloudrun on GCP, or container instances on Azure)
-  - 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/)
+  - 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/) to push this task as far to the left as possible (dev side)
 
 
 <br/><br/>
@@ -55,6 +59,8 @@ In what [Sysdig For Cloud Features](https://docs.sysdig.com/en/docs/sysdig-secur
 
 With both examples `single` and `org`, you can customize the desired features to de deployed with the `deploy_*` input vars to avoid deploying more than wanted.
 
+<br/>
+
 ### Compute Workload Type
 
 | Cloud | Example Options |
@@ -64,6 +70,7 @@ With both examples `single` and `org`, you can customize the desired features to
 | Azure | K8S `-k8s`, AzureContainerInstances |
 
 <br/><br/>
+
 ## Available Optionals
 
 We enable following optionals, to allow user to re-use their pre-existing / configured resources.
@@ -74,5 +81,5 @@ We enable following optionals, to allow user to re-use their pre-existing / conf
 | | ECS, VPC, Subnet | `ecs_cluster_name`, `ecs_vpc_id`, `ecs_vpc_subnets_private_ids` | if used, the three are mandatory  |
 | GCP | - | - | - |
 | Azure | ResourceGroup | `resource_group_name` | - |
-| | ACR (registry)  | `registry_name`, `registry_resource_group_name` | - | 
+| | ACR | `registry_name`, `registry_resource_group_name` | - | 
 | * | Compute Workload | - | All clouds allow Sysdig Secure for cloud to be deployed on a pre-existing K8S cluster|