Skip to content

Commit

Permalink
[fix] SSM compliance (#13)
Browse files Browse the repository at this point in the history
* [fix] SSM compliance
  • Loading branch information
aquamatthias authored May 14, 2024
1 parent 642c1ca commit b72f1ca
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ jobs:
packages_dir: ./dist/

- name: Trigger workflow in fixinventory repo
if: ${{ github.actor != 'someci' }}
if: github.ref_type == 'tag' && github.actor != 'someci'
env:
GITHUB_TOKEN: ${{ secrets.SOME_CI_PAT }}
run: |
Expand Down
2 changes: 1 addition & 1 deletion fixcompliance/data/checks/aws/aws_ssm.json
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@
"risk": "Non-compliance of AWS resources (EC2, DynamoDB, SSM, S3) with AWS Systems Manager policies could expose security vulnerabilities, and incite operational inconsistencies. This could infringe regulatory compliance laws risking system integrity, data safety, and reliability.",
"severity": "high",
"detect": {
"fix": "is(aws_ssm_resource_compliance) --> is(aws_ec2_instance, aws_dynamodb_table, aws_ssm_document, aws_s3_bucket)"
"fix": "is(aws_ssm_resource_compliance) and status=NON_COMPLIANT --> is(aws_ec2_instance, aws_dynamodb_table, aws_ssm_document, aws_s3_bucket)"
},
"remediation": {
"text": "To rectify non-compliance, identify the unmet AWS Systems Manager standards for each resource. Ensure proper setup of SSM Agent for EC2 instances, verify table settings for DynamoDB against best practices, fix S3 bucket's access controls and encryption settings. Enforce compliance policies, perform consistent audits, and leverage AWS Systems Manager automation to mend non-compliant resources.",
Expand Down

0 comments on commit b72f1ca

Please sign in to comment.