v0.0.6

What's Changed

Added support for Composite Alerts

• fixes (#15) by @jbonner7 in #17
• fixes (#16) by @jbonner7 in #18
• fixes (#19) by @jbonner7 in #20
• Updates to (#19) by @jbonner7 in #21

Full Changelog: v0.0.5...v0.0.6

v0.0.5

What's Changed

• Updates to README by @jbonner7 to align with https://docs.fortinet.com/document/lacework-forticnapp/latest/administration-guide/963651/amazon-security-lake-alert-channel

Full Changelog: v0.0.4...v0.0.5

v0.0.4

What's Changed

• Updated README by @jbonner7

Full Changelog: v0.0.3...v0.0.4

v0.0.3

What's Changed

• Various Updates to Lacework.go by @jbonner7 in #14 (fixed #13)

Full Changelog: v0.0.2...v0.0.3

v0.0.2

What's Changed

#11 - Update Lacework.go CT_USER.MFA struct from bool to int to resolve unmarshall error in #12

Full Changelog: v0.0.1...v0.0.2

v0.0.1

What's Changed

• fixes (#9) by @jbonner7 in #10

Full Changelog: v0.0.0...v0.0.1

v0.0.0

What's Changed

• Update python and go runtime versions. Refactor Go binaries and Lambda functions: Fix #1 by @jbonner7 in #2
• #3 Update CloudFormation yaml and bootstrap with external ID as required by Amazon Security Lake: by @jbonner7 in #4
• Mask external ID and other sensitive values in CloudWatch Logs: fixes (#5) by @jbonner7 in #6
• Update Go structs for Lacework alert types : fixes (#7) by @jbonner7 in #8
• Revert changes to OSCF mapping for Root Usage: #9

Full Changelog: https://github.com/lacework-alliances/amazon-security-lake/commits/v0.0.0