Skip to content

fix: address SFI security compliance issues#435

Open
Prachig-Microsoft wants to merge 2 commits into
devfrom
feature/sfi-security-fixes
Open

fix: address SFI security compliance issues#435
Prachig-Microsoft wants to merge 2 commits into
devfrom
feature/sfi-security-fixes

Conversation

@Prachig-Microsoft
Copy link
Copy Markdown

  • Enable infrastructure encryption (double encryption) for storage account
  • Add Security solution to Log Analytics workspace for SecurityEvent table
  • Add Windows Security Audit Event Logs (EventID 4624/4625) to data collection rules
  • Route Microsoft-SecurityEvent stream to Log Analytics in both main.bicep and main_custom.bicep

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

- Enable infrastructure encryption (double encryption) for storage account
- Add Security solution to Log Analytics workspace for SecurityEvent table
- Add Windows Security Audit Event Logs (EventID 4624/4625) to data collection rules
- Route Microsoft-SecurityEvent stream to Log Analytics in both main.bicep and main_custom.bicep

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses SFI security compliance by enabling infrastructure (double) encryption on the storage account and onboarding the Security solution + Windows Security Audit events (EventIDs 4624/4625) to Log Analytics via the data collection rule, in both the standard and custom infra templates.

Changes:

  • Enable requireInfrastructureEncryption: true on the storage account module.
  • Deploy a Microsoft.OperationsManagement/solutions "Security" solution to the LA workspace when private networking + monitoring are enabled, and gate the DCR module on it.
  • Add a Microsoft-SecurityEvent windows event log data source and matching LA dataflow to the DCR (and fix the stream from Microsoft-WindowsEvent to Microsoft-SecurityEvent in main_custom.bicep).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
infra/modules/storageAccount.bicep Turns on infrastructure (double) encryption.
infra/main.bicep Adds Security solution resource + Windows Security Event data source/dataflow in DCR.
infra/main_custom.bicep Same Security solution + DCR additions; corrects stream name to Microsoft-SecurityEvent.
infra/main.json Regenerated ARM JSON reflecting the above (template hashes, security solution, DCR updates, double encryption).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread infra/main.bicep Outdated
Comment thread infra/main.bicep Outdated
Revert the Microsoft.OperationsManagement/solutions 'Security' resource and the Microsoft-SecurityEvent data source/dataflow added in the previous commit. The SecurityEvent table is not provisioned by OMSGallery/Security in modern subscriptions and this workload has no Windows VMs to source the events, which was causing 'InvalidOutputTable' deployment failures. Retain only the storage account double-encryption change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants