Use the links below to navigate to specific projects or subject tags:
| PROJECTS: | Azure AI Security Challenge | Sentinel-as-Code | ** | ** | ** | |||||||||||||||||
| SUBJECTS: | Security | Automation | Ai | ** | ** | |||||||||||||||||
| AZURE RESOURCES: | Sentinel | Log Analytics Workspace | Defender XDR | Purview | Priva | |||||||||||||||||
| AZURE RESOURCES CONT.: | Entra ID | Fabric | ** | ** | ** | |||||||||||||||||
| DEV PLATFORMS: | GitHub | Azure DevOps | ** | ** | ** | |||||||||||||||||
| CODING: | PowerShell | YAML | ** | ** | ** |
Azure AI Security Skills Challenge
Version: 0.0.2
Author: Marcus Jacobson
License: MIT
Repository: GitHub
Project Status
- Week 0: ✅ COMPLETE
- Week 1: ✅ COMPLETE
- Week 2: Not Started
- Week 3: Not Started
- Week 4: Not Started
- Week 5: Not Started
- Week 6: Not Started
- Week 7: Not Started
- Week 8: Not Started
- Week 9: Not Started
⚠️ Important Project Update: This project has been restructured from a 12-week to a 9-week focused learning path based on lessons learned during Week 1. The new structure provides a more logical progression and realistic time investment for working professionals.
Microsoft Sentinel-as-Code
Version: 1.0.0
Author: Marcus Jacobson
License: MIT
Repository: GitHub
Project Status
- Foundation Infrastructure: COMPLETE
- Analytics Rules (NRT): COMPLETE
- Analytics Rules (Scheduled): COMPLETE
- Watchlist Automation: COMPLETE
- Hunting Queries: Planned
- Automation Rules: Planned
- Workbooks: Planned
- Data Connectors: Available via Content Hub
Project Goal
This project provides a comprehensive automation framework for deploying and managing Microsoft Sentinel environments using Azure DevOps Pipelines. The framework enables organizations to implement security operations at scale with consistency, repeatability, and governance through Infrastructure as Code (IaC) principles.
GitHub & AzDO - Sync an existing AzureDevOps Repository to GitHub
Version: 1.0.0
Author: Marcus Jacobson
License: MIT
Repository: GitHub
Project Goal
Create a one-way sync from Azure DevOps to GitHub, for the purpose of publishing projects created in Azure DevOps to the shareable GitHub repo.
Project Outcomes
Upon running the pipeline in AzureDevops, any new or changed files in the Azure DevOps repo will be updated in the GitHub repository.
Limitations:
- Due to the allowable permissions for GitHub personal access tokens, only read & write permissions are allowed, but delete permissions are not available. Therefore any deleted files in the Azure DevOps will not be deleted in GitHub.
- Any files that are moved within Azure DevOps will be duplicated, one version in each locations. Therefore any deleted or moved files will need to be manually remediated in GitHub.
- Another remediation option would be to empty the GitHub repository and then run the pipeline again in Azure DevOps. This will make sure that only the most recent files and folder structure is live in GitHub.
Features
There are three files that are included as part of this project: