From 6a957737a1030cc664934f2d98a34737ebe19b98 Mon Sep 17 00:00:00 2001 From: JimmyDuong00 Date: Tue, 6 Aug 2024 07:34:38 -0700 Subject: [PATCH] projects --- ...plying SP800-53 to Azure Infrastructure.md | 2 + ...ecured CCTV cameras using Bash scripts.md" | 0 ...brid organizations using Entra Connect.md" | 0 content/2 Azure Services/Access Reviews.md | 2 +- content/2 Azure Services/Azure Initiative.md | 2 +- .../Obtaining Hardware ID for Autopilot.md | 11 ++++ .../Terraform Associate (003).md | 53 +++++++++++++++++ .../Certifications/Terraform Associate 003.md | 57 ------------------- content/index.md | 2 +- 9 files changed, 69 insertions(+), 60 deletions(-) create mode 100644 "content/1 Projects/\360\237\216\245 Using Shodan to find and map unsecured CCTV cameras using Bash scripts.md" rename content/1 Projects/Connecting Azure to On Premesis.md => "content/1 Projects/\360\237\223\203 Connecting On-Prem Active Directory to Azure for hybrid organizations using Entra Connect.md" (100%) create mode 100644 content/2 Azure Services/Obtaining Hardware ID for Autopilot.md create mode 100644 content/Certifications/Terraform Associate (003).md delete mode 100644 content/Certifications/Terraform Associate 003.md diff --git a/content/1 Projects/Applying SP800-53 to Azure Infrastructure.md b/content/1 Projects/Applying SP800-53 to Azure Infrastructure.md index 1371817017d48..d74464978d8b7 100644 --- a/content/1 Projects/Applying SP800-53 to Azure Infrastructure.md +++ b/content/1 Projects/Applying SP800-53 to Azure Infrastructure.md @@ -2,3 +2,5 @@ draft: true --- We will use [[Azure Policy]] and [[Azure Initiative]] to secure and comply with NIST standards and guidelines. + + diff --git "a/content/1 Projects/\360\237\216\245 Using Shodan to find and map unsecured CCTV cameras using Bash scripts.md" "b/content/1 Projects/\360\237\216\245 Using Shodan to find and map unsecured CCTV cameras using Bash scripts.md" new file mode 100644 index 0000000000000..e69de29bb2d1d diff --git a/content/1 Projects/Connecting Azure to On Premesis.md "b/content/1 Projects/\360\237\223\203 Connecting On-Prem Active Directory to Azure for hybrid organizations using Entra Connect.md" similarity index 100% rename from content/1 Projects/Connecting Azure to On Premesis.md rename to "content/1 Projects/\360\237\223\203 Connecting On-Prem Active Directory to Azure for hybrid organizations using Entra Connect.md" diff --git a/content/2 Azure Services/Access Reviews.md b/content/2 Azure Services/Access Reviews.md index 0c47f170364c6..00df7c867ae59 100644 --- a/content/2 Azure Services/Access Reviews.md +++ b/content/2 Azure Services/Access Reviews.md @@ -3,7 +3,7 @@ tags: - azure - iam --- - +After assigning users a [[Privileged Identity Management (PIM)]] role, we can perform access reviews to ensure that users that need permissions will be allowed access to elevated systems. If not, they will be removed. In [[Entra ID]], navigate to the Identity Governance section: diff --git a/content/2 Azure Services/Azure Initiative.md b/content/2 Azure Services/Azure Initiative.md index df189142765ae..b0c79c980a75f 100644 --- a/content/2 Azure Services/Azure Initiative.md +++ b/content/2 Azure Services/Azure Initiative.md @@ -1,4 +1,4 @@ -To assign multiple polices at once we can use Initiative. +To assign multiple [[Azure Policy]] at once, we can use Initiative. In [[Azure Policy]], navigate to the Definitions and select initiative definition: diff --git a/content/2 Azure Services/Obtaining Hardware ID for Autopilot.md b/content/2 Azure Services/Obtaining Hardware ID for Autopilot.md new file mode 100644 index 0000000000000..09a62028bfec2 --- /dev/null +++ b/content/2 Azure Services/Obtaining Hardware ID for Autopilot.md @@ -0,0 +1,11 @@ +In order to on board an endpoint device, we need to obtain the hardware ID of the device. +We can use this Powershell Script below: + +``` +New-Item -Type Directory -Path "C:\HWID" +Set-Location -Path "C:\HWID" +$env:Path += ";C:\Program Files\WindowsPowershell\Scripts" +Set-ExecutionPolicy -Scope Processes -ExecutionPolicy RemoteSigned +Install-Script -Name Get-WindowsAutoPilotInfo +Get-WindowsAutopilotInfo -OutputFile AutoPilotHWID.csv +``` \ No newline at end of file diff --git a/content/Certifications/Terraform Associate (003).md b/content/Certifications/Terraform Associate (003).md new file mode 100644 index 0000000000000..bc4803d274314 --- /dev/null +++ b/content/Certifications/Terraform Associate (003).md @@ -0,0 +1,53 @@ +Here are some notes for the Terraform Associate Certification +I am planning to take this test by August 2024. + +## Exam Content Overview + +| **1** | **Understand Infrastructure as Code (IaC) concepts** | +| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1a | Explain what IaC is
IaC is provisioning infrastructure through code, instead of using clickops, we can reliably scale out resources across various providers through code in a standardized way.
| +| 1b | Describe advantages of IaC patterns
IaC patterns give us the consistency of software development practices into infrastructure deployment. | +| **2** | **Understand the purpose of Terraform (vs other IaC)** | +| 2a | Explain multi-cloud and provider-agnostic benefits
Multi cloud and provider-agnostic benefits in Terraform means that we can provision infrastructure using the same format for multi cloud environments compared to a single provider such as AWS's CloudFormation. | +| 2b | Explain the benefits of state
The benefits of state | +| **3** | **Understand Terraform basics** | +| 3a | Install and version Terraform providers | +| 3b | Describe plugin-based architecture | +| 3c | Write Terraform configuration using multiple providers | +| 3d | Describe how Terraform finds and fetches providers | +| **4** | **Use Terraform outside the core workflow** | +| 4a | Describe when to use `terraform import` to import existing infrastructure into your Terraform state | +| 4b | Use `terraform state` to view Terraform state | +| 4c | Describe when to enable verbose logging and what the outcome/value is | +| **5** | **Interact with Terraform modules** | +| 5a | Contrast and use different module source options including the public Terraform Registry | +| 5b | Interact with module inputs and outputs | +| 5c | Describe variable scope within modules/child modules | +| 5d | Set module version | +| **6** | **Use the core Terraform workflow** | +| 6a | Describe Terraform workflow ( Write -> Plan -> Create ) | +| 6b | Initialize a Terraform working directory (`terraform init`) | +| 6c | Validate a Terraform configuration (`terraform validate`) | +| 6d | Generate and review an execution plan for Terraform (`terraform plan`) | +| 6e | Execute changes to infrastructure with Terraform (`terraform apply`) | +| 6f | Destroy Terraform managed infrastructure (`terraform destroy`) | +| 6g | Apply formatting and style adjustments to a configuration (`terraform fmt`) | +| **7** | **Implement and maintain state** | +| 7a | Describe default `local` backend | +| 7b | Describe state locking | +| 7c | Handle backend and cloud integration authentication methods | +| 7d | Differentiate remote state back end options | +| 7e | Manage resource drift and Terraform state | +| 7f | Describe `backend` block and cloud integration in configuration | +| 7g | Understand secret management in state files | +| **8** | **Read, generate, and modify configuration** | +| 8a | Demonstrate use of variables and outputs | +| 8b | Describe secure secret injection best practice | +| 8c | Understand the use of collection and structural types | +| 8d | Create and differentiate `resource` and `data` configuration | +| 8e | Use resource addressing and resource parameters to connect resources together | +| 8f | Use HCL and Terraform functions to write configuration | +| 8g | Describe built-in dependency management (order of execution based) | +| **9** | **Understand HCP Terraform capabilities** | +| 9a | Explain how HCP Terraform helps to manage infrastructure | +| 9b | Describe how HCP Terraform enables collaboration and governance | diff --git a/content/Certifications/Terraform Associate 003.md b/content/Certifications/Terraform Associate 003.md deleted file mode 100644 index 594467b6cfb3e..0000000000000 --- a/content/Certifications/Terraform Associate 003.md +++ /dev/null @@ -1,57 +0,0 @@ -Here are some notes for the Terraform Associate Certification -I am planning to take this test by August 2024. - -## **1** **Understand Infrastructure as Code (IaC) concepts** -### Explain what IaC is -IaC is - - -| | | -| ----- | --------------------------------------------------------------------------------------------------- | -| **1** | **Understand Infrastructure as Code (IaC) concepts** | -| 1a | Explain what IaC is
| -| 1b | Describe advantages of IaC patterns
IaC patterns | -| **2** | **Understand the purpose of Terraform (vs other IaC)** | -| 2a | Explain multi-cloud and provider-agnostic benefits | -| 2b | Explain the benefits of state | -| **3** | **Understand Terraform basics** | -| 3a | Install and version Terraform providers | -| 3b | Describe plugin-based architecture | -| 3c | Write Terraform configuration using multiple providers | -| 3d | Describe how Terraform finds and fetches providers | -| **4** | **Use Terraform outside the core workflow** | -| 4a | Describe when to use `terraform import` to import existing infrastructure into your Terraform state | -| 4b | Use `terraform state` to view Terraform state | -| 4c | Describe when to enable verbose logging and what the outcome/value is | -| **5** | **Interact with Terraform modules** | -| 5a | Contrast and use different module source options including the public Terraform Registry | -| 5b | Interact with module inputs and outputs | -| 5c | Describe variable scope within modules/child modules | -| 5d | Set module version | -| **6** | **Use the core Terraform workflow** | -| 6a | Describe Terraform workflow ( Write -> Plan -> Create ) | -| 6b | Initialize a Terraform working directory (`terraform init`) | -| 6c | Validate a Terraform configuration (`terraform validate`) | -| 6d | Generate and review an execution plan for Terraform (`terraform plan`) | -| 6e | Execute changes to infrastructure with Terraform (`terraform apply`) | -| 6f | Destroy Terraform managed infrastructure (`terraform destroy`) | -| 6g | Apply formatting and style adjustments to a configuration (`terraform fmt`) | -| **7** | **Implement and maintain state** | -| 7a | Describe default `local` backend | -| 7b | Describe state locking | -| 7c | Handle backend and cloud integration authentication methods | -| 7d | Differentiate remote state back end options | -| 7e | Manage resource drift and Terraform state | -| 7f | Describe `backend` block and cloud integration in configuration | -| 7g | Understand secret management in state files | -| **8** | **Read, generate, and modify configuration** | -| 8a | Demonstrate use of variables and outputs | -| 8b | Describe secure secret injection best practice | -| 8c | Understand the use of collection and structural types | -| 8d | Create and differentiate `resource` and `data` configuration | -| 8e | Use resource addressing and resource parameters to connect resources together | -| 8f | Use HCL and Terraform functions to write configuration | -| 8g | Describe built-in dependency management (order of execution based) | -| **9** | **Understand HCP Terraform capabilities** | -| 9a | Explain how HCP Terraform helps to manage infrastructure | -| 9b | Describe how HCP Terraform enables collaboration and governance | diff --git a/content/index.md b/content/index.md index 2cc6581a424d5..a8802f7b42f97 100644 --- a/content/index.md +++ b/content/index.md @@ -62,7 +62,7 @@ EC-Council: Hashicorp: -[[Terraform Associate 003]] +[[Terraform Associate (003)]] ISC2: