diff --git a/.gitignore b/.gitignore index 337ec91..a5c228f 100644 --- a/.gitignore +++ b/.gitignore @@ -163,3 +163,5 @@ override.tf.json # Ignore CLI configuration files .terraformrc terraform.rc + +*.DS_Store diff --git a/README.md b/README.md index fc435e2..804a90d 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,6 @@ A collection of projects supporting GCP integration * Container Security * [Falcon Container Security Documents](container) * VM Sensor Deployment - * [Google OS Config](osconfig) + * [Google VM Manager (OSConfig)](osconfig) * Cloud Storage Security * [Cloud Storage Bucket Protection w/ QuickScan API](cloud-storage-protection) diff --git a/osconfig/.DS_Store b/osconfig/.DS_Store deleted file mode 100644 index 9ff5ee7..0000000 Binary files a/osconfig/.DS_Store and /dev/null differ diff --git a/osconfig/README.md b/osconfig/README.md index c900456..972def6 100644 --- a/osconfig/README.md +++ b/osconfig/README.md @@ -38,13 +38,13 @@ https://cloud.google.com/compute/docs/manage-os#agent-install If you have not created a key or do not know the secret for existing keys, you can create a new key by selecting “Add new api client” -![Alt text]() +![API Clients and Keys](images/API_Clients_and_Keys.png) Google will not be using any API access to your account and will simply use the API keys to verify that you are a current CrowdStrike customer. As such, you can delete the key later after deployment if you wish. Setup a new key as in the image below: -![Alt text]() +![Add new API Client](images/Add_new_API_Client.png) You are now ready to proceed to install. @@ -59,15 +59,15 @@ https://console.cloud.google.com/security/agent/deployment/crowdstrike 4) Customer ID: The CID for your CrowdStrike Account, copied from: https://falcon.crowdstrike.com/hosts/sensor-downloads -![Alt text]() +![CrowdStrike Falcon EPP](images/CrowdStrike_Falcon_EPP.png) Next, enter your Label key and Value from the Prerequisites section. You can also use VM Instance Name prefixs to target VMs. For example if all machines in the Dev group have the name “dev” prepended to the name, we can target machines like “dev-ib376”. -![Alt text]() +![CrowdStrike Falcon EPP](images/VM_Assignment.png) Finally, select an appropriate region for the sensor binaries to be copied to to stage them for install. -![Alt text]() +![CrowdStrike Falcon EPP](images/Storage_Bucket_Details.png) Clicking DEPLOY will deploy the sensor to the targeted images. You will be redirected to the hosts console of the CrowdStrike UI to check the status of new Hosts. This may take 10-15 minutes to appear depending on your configuration of the OS Config agent. Existing and new machines that match the policies label or name prefix targeting will have the sensor installed. diff --git a/osconfig/images/API Clients and Keys.png b/osconfig/images/API_Clients_and_Keys.png similarity index 100% rename from osconfig/images/API Clients and Keys.png rename to osconfig/images/API_Clients_and_Keys.png diff --git a/osconfig/images/Add new API Client.png b/osconfig/images/Add_new_API_Client.png similarity index 100% rename from osconfig/images/Add new API Client.png rename to osconfig/images/Add_new_API_Client.png diff --git a/osconfig/images/CrowdStrike Falcon EPP.png b/osconfig/images/CrowdStrike_Falcon_EPP.png similarity index 100% rename from osconfig/images/CrowdStrike Falcon EPP.png rename to osconfig/images/CrowdStrike_Falcon_EPP.png diff --git a/osconfig/images/Storage Bucket Details.png b/osconfig/images/Storage_Bucket_Details.png similarity index 100% rename from osconfig/images/Storage Bucket Details.png rename to osconfig/images/Storage_Bucket_Details.png diff --git a/osconfig/images/VM Assignment.png b/osconfig/images/VM_Assignment.png similarity index 100% rename from osconfig/images/VM Assignment.png rename to osconfig/images/VM_Assignment.png