bcgov / bcgov/cloud-pathfinder

AWS SIEM development with SecOps - lab setup

Open
#2,766 2 comments 0 reactions 1 assignee Claimed by @NickCorcoran View on GitHub
Security
Dominant language
Jinja
Stars
2
Forks
7
PR merge metrics
No merged PRs in 30d

Description

**Describe the Issue**
While we initially stood up a SIEM using OpenSearch, we needed to scale down usage due to costs for our team.
SecOps has a desire to re-instate this capability, and it is very likely they will help cover the cost.
We will stand up a the SecOps lab environment to closely mirror what we have in our ASEA and prep for rollout to Forge.

**Additional Context**
Add any other context, attachments or screenshots

**Acceptance Criteria**
- [x] Review existing scaled down setup in ASEA
- [x] Stand up toolset in SecOps lab (SecOps will be doing this work)
- [ ] Set some initial consumption/alert rulesets (starting small)
- [ ] Review with Prabhu/Warren

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.