Update huawei-holosense-panel template with improved metadata and structure

- Added reference to official Huawei product page - Fixed max-request vs max-requests field naming for consistency - Added panel and iot tags for better categorization - Enhanced template structure following review guidelines
Fix yamllint
2026-11-07 16:39:20 -10:00 · 2025-07-15 18:19:44 +04:00 · 2025-07-14 22:55:44 +02:00 · 2025-07-14 22:49:48 +02:00 · 2025-07-14 22:37:19 +02:00 · 2025-07-14 11:06:47 +00:00
10957 changed files with 561609 additions and 37855 deletions
@@ -7,8 +7,8 @@ password = sys.argv[3]

 repo_owner = "projectdiscovery"
 repo_name = "nuclei-templates"
-pr_user_list = ["DhiyaneshGeek", "ritikchaddha"]
-issue_user_list = ["DhiyaneshGeek", "ritikchaddha", "princechaddha"]
+pr_user_list = ["pussycat0x", "DhiyaneshGeek", "ritikchaddha"]
+issue_user_list = ["DhiyaneshGeek", "ritikchaddha", "pussycat0x", "princechaddha"]

 headers = {'Authorization': f'Bearer {password}',
        'Accept': 'application/vnd.github+json',
@@ -1,9 +1,9 @@
 name: 🤖 issue/pr assignment
 on:
-  pull_request:
-    types: [opened]
-    branches: 
-      - main
+#  pull_request:
+#    types: [opened]
+#    branches: 
+#      - main
  issues:
    types: [opened]

@@ -20,7 +20,7 @@ jobs:
        with:
          python-version: '3.10' # install the python version needed
      - run: pip install requests
-      - if: github.event_name == 'pull_request'
-        run: python .github/scripts/assign_tasks.py ${{ github.event.pull_request.number }} pr ${{ secrets.GITHUB_TOKEN }}
+#      - if: github.event_name == 'pull_request'
+#        run: python .github/scripts/assign_tasks.py ${{ github.event.pull_request.number }} pr ${{ secrets.GITHUB_TOKEN }}
      - if: github.event_name == 'issues'
        run: python .github/scripts/assign_tasks.py ${{ github.event.issue.number }} issue ${{ secrets.GITHUB_TOKEN }}
@@ -33,8 +33,3 @@ jobs:
      - run: |
          git pull origin $GITHUB_REF --rebase
          git push origin $GITHUB_REF
-
-  sync:
-    needs: new-addition
-    uses: ./.github/workflows/templates-sync.yml
-    secrets: inherit
@@ -1,21 +0,0 @@
-name: 📑 Template-DB Indexer
-
-on:
-  push:
-    tags:
-      - '*'
-  workflow_dispatch:
-
-jobs:
-  index:
-    runs-on: ubuntu-latest
-    if: github.repository == 'projectdiscovery/nuclei-templates'
-    steps:
-      - uses: projectdiscovery/actions/generate/db-indexer@v1
-        with:
-          token: '${{ secrets.ACCESS_TOKEN }}'
-          mode: 'templates'
-          args: '-eft'
-        env:
-          AWS_ACCESS_KEY: ${{ secrets.AWS_ACCESS_KEY }}
-          AWS_SECRET_KEY: ${{ secrets.AWS_SECRET_KEY }}
@@ -9,12 +9,15 @@ on:
  workflow_dispatch:

 jobs:
-  build:
+  linux-sign:
+    name: Sign All Templates (Linux)
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
      - uses: actions/checkout@v4
      - uses: projectdiscovery/actions/setup/nuclei@v1
+        with:
+          token: '${{ secrets.GITHUB_TOKEN}}'
      - run: nuclei -lfa -duc -sign -ud $GITHUB_WORKSPACE -t .
        env:
          NUCLEI_USER_CERTIFICATE: ${{ secrets.NUCLEI_USER_CERTIFICATE }}
@@ -28,3 +31,48 @@ jobs:
        run: |
          git pull origin $GITHUB_REF --rebase
          git push origin $GITHUB_REF
+
+  windows-sign:
+    name: Sign Windows Templates
+    needs: linux-sign
+    runs-on: windows-latest
+    if: github.repository == 'projectdiscovery/nuclei-templates'
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version: '1.21'
+          
+      - name: Install Nuclei
+        run: |
+          go install -v github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest
+          nuclei -version
+        shell: bash
+          
+      - name: Sign Windows Templates
+        run: nuclei -lfa -duc -sign -ud "${{ github.workspace }}" -t "code/windows/audit"
+        shell: bash
+        env:
+          NUCLEI_USER_CERTIFICATE: ${{ secrets.NUCLEI_USER_CERTIFICATE }}
+          NUCLEI_USER_PRIVATE_KEY: ${{ secrets.NUCLEI_USER_PRIVATE_KEY }}
+          
+      - name: Configure Git
+        run: |
+          git config --global user.name "Ghost"
+          git config --global user.email "[email protected]"
+        shell: bash
+          
+      - name: Commit Changes
+        run: |
+          git add code/windows/audit
+          git commit -m "chore: re-sign windows templates 🤖" || echo "No changes to commit"
+        shell: bash
+          
+      - name: Push Changes
+        run: |
+          git remote update
+          git pull origin ${{ github.ref }} --rebase || exit 1
+          git push origin ${{ github.ref }} || (git remote update && git pull origin ${{ github.ref }} --rebase && git push origin ${{ github.ref }})
+        shell: bash
@@ -11,7 +11,7 @@ jobs:
      - uses: actions/checkout@v4
      - uses: projectdiscovery/actions/setup/templateman@v1
        with:
-          token: '${{ secrets.ACCESS_TOKEN }}'
+          token: '${{ secrets.PDTEAMX_CLASSIC_PAT }}'
      - run: tmc -mr -e -at <<< "$(pwd)"
      - uses: projectdiscovery/actions/setup/git@v1
      - uses: projectdiscovery/actions/commit@v1
@@ -1,64 +0,0 @@
-name: Sync Repositories Workflow
-on:
-  push:
-    paths:
-    - '.new-additions'
-    - '.github/scripts/yaml2json/go.mod'
-    - '.github/scripts/yaml2json/go.sum'
-    - '.github/workflows/tests.yml'
-    - 'CVE-2024-7339.yaml'
-    - 'http/cves/2022/CVE-2022-27043.yaml'
-    - 'http/cves/2023/CVE-2023-43323.yaml'
-    - 'http/cves/2023/CVE-2023-44393.yaml'
-    - 'http/cves/2023/CVE-2023-5222.yaml'
-    - 'http/cves/2024/CVE-2024-24763.yaml'
-    - 'http/cves/2024/CVE-2024-34061.yaml'
-    - 'http/cves/2024/CVE-2024-36104.yaml'
-    - 'http/cves/2024/CVE-2024-38856.yaml'
-    - 'http/cves/2024/CVE-2024-39903.yaml'
-    - 'http/cves/2024/CVE-2024-39907.yaml'
-    - 'http/cves/2024/CVE-2024-40422.yaml'
-    - 'http/cves/2024/CVE-2024-41107.yaml'
-    - 'http/cves/2024/CVE-2024-41628.yaml'
-    - 'http/cves/2024/CVE-2024-5975.yaml'
-    - 'http/cves/2024/CVE-2024-6205.yaml'
-    - 'http/cves/2024/CVE-2024-6366.yaml'
-    - 'http/cves/2024/CVE-2024-6396.yaml'
-    - 'http/cves/2024/CVE-2024-6781.yaml'
-    - 'http/cves/2024/CVE-2024-6782.yaml'
-    - 'http/cves/2024/CVE-2024-6922.yaml'
-    - 'http/cves/2024/CVE-2024-7008.yaml'
-    - 'http/cves/2024/CVE-2024-7120.yaml'
-    - 'http/cves/2024/CVE-2024-7188.yaml'
-    - 'http/cves/2024/CVE-2024-7332.yaml'
-    - 'http/cves/2024/CVE-2024-7340.yaml'
-    - 'http/default-logins/apache/cloudstack-default-login.yaml'
-    - 'http/exposed-panels/airos-panel.yaml'
-    - 'http/exposed-panels/metube-panel.yaml'
-    - 'http/exposed-panels/openedge-panel.yaml'
-    - 'http/exposed-panels/whatsup-gold-panel.yaml'
-    - 'http/exposures/files/gitlab-ci-yml.yaml'
-    - 'http/misconfiguration/changedetection-unauth.yaml'
-    - 'http/misconfiguration/deployment-interface-exposed.yaml'
-    - 'http/misconfiguration/installer/quickcms-installer.yaml'
-    - 'http/misconfiguration/manage-cabinet-register.yaml'
-    - 'http/osint/user-enumeration/substack.yaml'
-    - 'http/technologies/apache/apache-ofbiz-detect.yaml'
-    - 'http/technologies/apache/apache-shenyu-detect.yaml'
-    - 'http/technologies/searxng-detect.yaml'
-    - 'http/vulnerabilities/esafenet/esafenet-netsecconfigajax-sqli.yaml'
-    - 'http/vulnerabilities/esafenet/esafenet-noticeajax-sqli.yaml'
-    - 'http/vulnerabilities/landray/landray-oa-replaceextend-rce.yaml'
-    - 'javascript/misconfiguration/x11/x11-unauth-access.yaml'
-    - 'javascript/udp/detection/db2-discover.yaml'
-  workflow_dispatch:
-  workflow_call:
-
-jobs:
-  sync:
-    if: github.repository == 'projectdiscovery/nuclei-templates'
-    runs-on: ubuntu-latest
-    steps:
-    - uses: projectdiscovery/actions/templates/sync@v1
-      with:
-        token: ${{ secrets.GTOKEN }}
@@ -25,6 +25,8 @@ jobs:
    steps:
      - uses: actions/checkout@v4
      - uses: projectdiscovery/actions/setup/nuclei@v1
+        with:
+          token: '${{ secrets.GITHUB_TOKEN }}'
      - name: Validate templates
        run: nuclei -duc -validate -lfa -ud $GITHUB_WORKSPACE -w workflows/ -et .github/

@@ -32,6 +34,9 @@ jobs:
    needs: lint
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
+    permissions:
+      issues: write
+      pull-requests: write
    env:
      HONEYPOT_URL: 'http://honey.scanme.sh'
    steps:
@@ -48,6 +53,8 @@ jobs:
            changed:
              - added|modified: *templates
      - uses: projectdiscovery/actions/setup/nuclei@v1
+        with:
+          token: '${{ secrets.GITHUB_TOKEN }}'
      - run: bash weak-matcher-checks.sh
        id: check
        if: steps.filter.outputs.changed == 'true'
@@ -73,3 +80,4 @@ jobs:
            })
        env:
          COMMENT: '${{ steps.check.outputs.comment }}'
+          GITHUB_TOKEN: '${{ secrets.PDTEAMX_CLASSIC_PAT }}'
@@ -1,116 +1,81 @@
-cloud/aws/dms/dms-multi-az.yaml
-cloud/aws/dms/dms-public-access.yaml
-cloud/aws/dms/dms-version-upgrade.yaml
-cloud/aws/ebs/ebs-encryption-disabled.yaml
-cloud/aws/efs/efs-encryption-disabled.yaml
-cloud/aws/elasticache/cache-automatic-backups-disabled.yaml
-cloud/aws/elasticache/cache-event-notification-disabled.yaml
-cloud/aws/elasticache/cache-redis-encryption-disabled.yaml
-cloud/aws/elasticache/cache-redis-multiaz-disabled.yaml
-cloud/aws/firehose/firehose-server-destination-encryption.yaml
-cloud/aws/firehose/firehose-server-side-encryption.yaml
-cloud/aws/guardduty/guardduty-findings.yaml
-cloud/aws/guardduty/guardduty-not-enabled.yaml
-cloud/aws/guardduty/malware-protection-disabled.yaml
-cloud/aws/guardduty/s3-protection-disabled.yaml
-cloud/aws/inspector2/inspector2-disabled.yaml
-cloud/aws/rds/rds-auto-minor-upgrade-disabled.yaml
-cloud/aws/rds/rds-automated-backup-disabled.yaml
-cloud/aws/rds/rds-backtrack-disabled.yaml
-cloud/aws/rds/rds-cluster-protection-disabled.yaml
-cloud/aws/rds/rds-copy-snap.yaml
-cloud/aws/rds/rds-insights-disabled.yaml
-cloud/aws/rds/rds-instance-autoscaling-disabled.yaml
-cloud/aws/rds/rds-log-export-disabled.yaml
-cloud/aws/rds/rds-multi-az.yaml
-cloud/aws/rds/rds-public-access.yaml
-cloud/aws/route53/route53-dns-query-disabled.yaml
-cloud/aws/route53/route53-dnssec-signing-disabled.yaml
-dast/cves/2024/CVE-2024-2961.yaml
-http/cnvd/2024/CNVD-2024-38747.yaml
-http/cves/2015/CVE-2015-8562.yaml
-http/cves/2016/CVE-2016-9299.yaml
-http/cves/2017/CVE-2017-5868.yaml
-http/cves/2018/CVE-2018-7192.yaml
-http/cves/2018/CVE-2018-7193.yaml
-http/cves/2018/CVE-2018-7196.yaml
-http/cves/2019/CVE-2019-8943.yaml
-http/cves/2021/CVE-2021-38156.yaml
-http/cves/2021/CVE-2021-45811.yaml
-http/cves/2023/CVE-2023-1315.yaml
-http/cves/2023/CVE-2023-1317.yaml
-http/cves/2023/CVE-2023-1318.yaml
-http/cves/2023/CVE-2023-2745.yaml
-http/cves/2023/CVE-2023-38040.yaml
-http/cves/2023/CVE-2023-39560.yaml
-http/cves/2023/CVE-2023-40748.yaml
-http/cves/2023/CVE-2023-40749.yaml
-http/cves/2023/CVE-2023-40750.yaml
-http/cves/2023/CVE-2023-40751.yaml
-http/cves/2023/CVE-2023-40752.yaml
-http/cves/2023/CVE-2023-40753.yaml
-http/cves/2023/CVE-2023-40755.yaml
-http/cves/2023/CVE-2023-40931.yaml
-http/cves/2023/CVE-2023-43373.yaml
-http/cves/2023/CVE-2023-5558.yaml
-http/cves/2023/CVE-2023-5561.yaml
-http/cves/2024/CVE-2024-22476.yaml
-http/cves/2024/CVE-2024-32735.yaml
-http/cves/2024/CVE-2024-32736.yaml
-http/cves/2024/CVE-2024-32737.yaml
-http/cves/2024/CVE-2024-32738.yaml
-http/cves/2024/CVE-2024-32739.yaml
-http/cves/2024/CVE-2024-35584.yaml
-http/cves/2024/CVE-2024-3656.yaml
-http/cves/2024/CVE-2024-39713.yaml
-http/cves/2024/CVE-2024-43360.yaml
-http/cves/2024/CVE-2024-44349.yaml
-http/cves/2024/CVE-2024-4439.yaml
-http/cves/2024/CVE-2024-45216.yaml
-http/cves/2024/CVE-2024-45488.yaml
-http/cves/2024/CVE-2024-46310.yaml
-http/cves/2024/CVE-2024-48914.yaml
-http/cves/2024/CVE-2024-49757.yaml
-http/cves/2024/CVE-2024-5910.yaml
-http/cves/2024/CVE-2024-8698.yaml
-http/cves/2024/CVE-2024-9061.yaml
-http/cves/2024/CVE-2024-9234.yaml
-http/cves/2024/CVE-2024-9593.yaml
-http/cves/2024/CVE-2024-9617.yaml
-http/cves/2024/CVE-2024-9796.yaml
-http/default-logins/apache/doris-default-login.yaml
-http/default-logins/sato/sato-default-login.yaml
-http/default-logins/zebra/zebra-printer-default-login.yaml
-http/exposed-panels/1password-scim-panel.yaml
-http/exposed-panels/danswer-panel.yaml
-http/exposed-panels/freescout-panel.yaml
-http/exposed-panels/nagios/nagios-logserver-panel.yaml
-http/exposed-panels/olympic-panel.yaml
-http/exposed-panels/onedev-panel.yaml
-http/exposed-panels/paloalto-expedition-panel.yaml
-http/exposed-panels/reolink-panel.yaml
-http/exposed-panels/sqlpad-panel.yaml
-http/exposed-panels/traccar-panel.yaml
-http/exposed-panels/txadmin-panel.yaml
-http/exposed-panels/usermin-panel.yaml
-http/exposed-panels/veritas-netbackup-panel.yaml
-http/exposed-panels/vmware-aria-panel.yaml
-http/misconfiguration/installer/nagios-logserver-installer.yaml
-http/misconfiguration/redpanda-console.yaml
-http/misconfiguration/root-path-disclosure.yaml
-http/misconfiguration/unauth-cyber-power-systems.yaml
-http/takeovers/wasabi-bucket-takeover.yaml
-http/technologies/accellion-detect.yaml
-http/technologies/gradio-detect.yaml
-http/technologies/lollms-webui-detect.yaml
-http/technologies/mirth-connect-detect.yaml
-http/technologies/oracle-fusion-detect.yaml
-http/technologies/salesforce-b2c-commerce-webdav.yaml
-http/vulnerabilities/hcm/hcm-cloud-lfi.yaml
-http/vulnerabilities/nagios/nagios-xi-xss.yaml
-http/vulnerabilities/other/cyberpanel-rce.yaml
-http/vulnerabilities/wordpress/application-pass-xss.yaml
-http/vulnerabilities/wordpress/wp-footnote-xss.yaml
-http/vulnerabilities/yonyou/yonyou-u8-crm-sqli.yaml
-http/vulnerabilities/yonyou/yonyou-u8-crm-tb-sqli.yaml
-passive/cves/2024/CVE-2024-40711.yaml
+code/cves/2022/CVE-2022-42475.yaml
+code/cves/2025/CVE-2025-6216.yaml
+code/windows/audit/kisa/account-lockout-threshold.yaml
+code/windows/audit/kisa/admin-account-rename.yaml
+code/windows/audit/kisa/admin-group-minimal.yaml
+code/windows/audit/kisa/autologon-control.yaml
+code/windows/audit/kisa/crash-on-audit-fail.yaml
+code/windows/audit/kisa/dns-zone-transfer-check.yaml
+code/windows/audit/kisa/ftp-access-control-check.yaml
+code/windows/audit/kisa/ftp-anonymous-check.yaml
+code/windows/audit/kisa/ftp-directory-permission-check.yaml
+code/windows/audit/kisa/hard-disk-default-share.yaml
+code/windows/audit/kisa/password-cleartext-encryption.yaml
+code/windows/audit/kisa/password-never-expires.yaml
+code/windows/audit/kisa/rds-removal-check.yaml
+code/windows/audit/kisa/remote-registry-access-check.yaml
+code/windows/audit/kisa/remote-system-shutdown.yaml
+code/windows/audit/kisa/sam-file-access-control.yaml
+code/windows/audit/kisa/service-pack-check.yaml
+code/windows/audit/kisa/shutdown-without-logon.yaml
+code/windows/audit/kisa/unnecessary-accounts-check.yaml
+code/windows/audit/kisa/unnecessary-service-check.yaml
+http/cves/2020/CVE-2020-9547.yaml
+http/cves/2020/CVE-2020-9548.yaml
+http/cves/2022/CVE-2022-23397.yaml
+http/cves/2023/CVE-2023-49230.yaml
+http/cves/2024/CVE-2024-50334.yaml
+http/cves/2025/CVE-2025-2010.yaml
+http/cves/2025/CVE-2025-27505.yaml
+http/cves/2025/CVE-2025-32813.yaml
+http/cves/2025/CVE-2025-32814.yaml
+http/cves/2025/CVE-2025-32815.yaml
+http/cves/2025/CVE-2025-34040.yaml
+http/cves/2025/CVE-2025-41646.yaml
+http/cves/2025/CVE-2025-4380.yaml
+http/cves/2025/CVE-2025-47812.yaml
+http/cves/2025/CVE-2025-47813.yaml
+http/cves/2025/CVE-2025-48827.yaml
+http/cves/2025/CVE-2025-49493.yaml
+http/cves/2025/CVE-2025-52488.yaml
+http/cves/2025/CVE-2025-53624.yaml
+http/cves/2025/CVE-2025-5777.yaml
+http/default-logins/molgenis/molgenis-default-login.yaml
+http/exposed-panels/cisco-cm-panel.yaml
+http/exposed-panels/cisco-prime-license-manager-panel.yaml
+http/exposed-panels/google-adk-api-exposed.yaml
+http/exposed-panels/google-adk-webui-exposed.yaml
+http/exposed-panels/molgenis-panel.yaml
+http/exposed-panels/peplink-panel.yaml
+http/exposed-panels/wingftp-panel.yaml
+http/miscellaneous/torrent-website-detect.yaml
+http/misconfiguration/dd-wrt-controlpanel-exposure.yaml
+http/misconfiguration/installer/pritunl-installer.yaml
+http/misconfiguration/twonky-server-exposure.yaml
+http/osint/user-enumeration/sessionize.yaml
+http/technologies/graphql/graphql-apiforwp-detect.yaml
+http/technologies/graphql/graphql-apollo-detect.yaml
+http/technologies/graphql/graphql-ariadne-detect.yaml
+http/technologies/graphql/graphql-dianajl-detect.yaml
+http/technologies/graphql/graphql-flutter-detect.yaml
+http/technologies/graphql/graphql-go-detect.yaml
+http/technologies/graphql/graphql-gqlgen-detect.yaml
+http/technologies/graphql/graphql-graphene-detect.yaml
+http/technologies/graphql/graphql-hasura-detect.yaml
+http/technologies/graphql/graphql-hypergraphql-detect.yaml
+http/technologies/graphql/graphql-java-detect.yaml
+http/technologies/graphql/graphql-juniper-detect.yaml
+http/technologies/graphql/graphql-php-detect.yaml
+http/technologies/graphql/graphql-ruby-detect.yaml
+http/technologies/graphql/graphql-sangria-detect.yaml
+http/technologies/graphql/graphql-strawberry-detect.yaml
+http/technologies/graphql/graphql-tartiflette-detect.yaml
+http/technologies/graphql/graphql-wpgraphql-detect.yaml
+http/technologies/wordpress/plugins/blocksy-companion.yaml
+http/technologies/wordpress/plugins/gosmtp.yaml
+http/technologies/wordpress/plugins/honeypot.yaml
+http/technologies/wordpress/plugins/pagelayer.yaml
+http/technologies/wordpress/plugins/siteseo.yaml
+http/technologies/wordpress/plugins/unlimited-elements-for-elementor.yaml
+http/vulnerabilities/infoblox/infoblox-netmri-rails-cookie-rce.yaml
+network/detection/jdwp-detect.yaml
@@ -25,11 +25,7 @@ tags:
 # unless asked for by the user.

 files:
-  - http/cves/2006/CVE-2006-1681.yaml
  - http/cves/2019/CVE-2019-14696.yaml
-  - http/cves/2020/CVE-2020-2036.yaml
-  - http/cves/2020/CVE-2020-28351.yaml
-  - http/vulnerabilities/oracle/oracle-ebs-xss.yaml
  - http/cves/2021/CVE-2021-28164.yaml
  - http/fuzzing/wordpress-themes-detect.yaml
  - http/fuzzing/mdb-database-file.yaml
@@ -0,0 +1,465 @@
+Nuclei-Templates is an open-source project featuring security checks written in YAML format, used by the Nuclei scanner.
+
+You are a reviewer for the GitHub repository: https://github.com/projectdiscovery/nuclei-templates. You will review a Pull Request (PR) diff, which may include new or updated templates, provided at the end of this prompt.
+
+Your objective is to thoroughly analyze the PR diff step-by-step and suggest improvements based solely on the context below. Begin your response by thanking the contributor and including: “You can join our [Discord server](https://discord.com/invite/projectdiscovery). It's a great place to connect with fellow contributors and stay updated with the latest developments. Thank you once again.”
+
+### Nuclei Templates Contribution Guide
+
+When submitting a new template, include these details with a proof of concept (P.O.C):
+
+1. `id`: A concise identifier (3-4 words, e.g., `grafana-unauth-rce`). For CVE templates, use the format `CVE-XXX-XXX`.
+2. Filename: Must match the template `id`.
+3. `name`: For vulnerability/CVE templates, use the format: `<Vendor> <Product> <Version> - Vulnerability`.
+4. `author`: Your GitHub/Twitter username or alias. Optionally, update [contributors.json](https://github.com/projectdiscovery/nuclei-templates/blob/master/contributors.json) with author details.
+5. `severity`: Based on CVSS score, adjusted for exploit impact and real-world implications.
+6. `description`: A brief summary of the vulnerability.
+7. `reference`: Include links to the POC, setup guide, or product details for verification.
+
+Best Practices:
+
+- Specify matcher location (e.g., `part: body` for response body).
+- Use `{{cmd}}` or `{{payloads}}` for RCE/injection templates, `{{username}}`/`{{password}}` for authenticated templates, and `{{token}}` for key/token templates.
+- For web shell uploads (last resort), use a random filename (`{{randstr}}`) and add the `intrusive` tag.
+- Add appropriate tags: `dos` for DoS templates, `auth` for authenticated templates, `cve` and `cve<year>` for CVE templates, `intrusive` for templates modifying configurations or files.
+- For XSS templates, include a unique endpoint string with the payload to avoid false positives (e.g., [CVE-2022-24899](https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-24899.yaml)).
+- For SSRF templates, include response-based matchers to reduce false positives from honeypots (see: https://github.com/projectdiscovery/nuclei-templates/issues/7401).
+- For time-based SQL injection templates, include a unique endpoint string with duration DSL to avoid false positives from network issues.
+
+Do’s:
+
+- Mark verified templates as `verified: true` and share debug data (redact sensitive server info).
+- Include multiple matchers to minimize false positives.
+- Provide a vulnerable environment (e.g., via [Vulhub](https://github.com/vulhub/vulhub)) when possible.
+- Include an active P.O.C in the template.
+
+Don’t:
+
+- Avoid weak matchers (e.g., strings from GET/POST data) to prevent false positives.
+- Do not make unnecessary changes to existing templates.
+- Avoid version-based CVE/exploit detection unless a full/partial POC is included. Exceptions (e.g., trending CVEs) require justification.
+
+### Templates Review Guide
+
+#### Functional Validation
+
+- Verify the reference to ensure the POC aligns with the template’s purpose (e.g., an RCE template must demonstrate RCE, not just version detection).
+- For XSS templates, confirm a unique endpoint string is included to avoid false positives.
+- Ensure sufficient, unique matchers to validate the issue without being overly strict.
+- For web templates, include at least two matchers (e.g., response header, status code).
+- For SSRF templates, add response-based matchers to counter honeypot triggers.
+- For time-based SQL injection templates, include a unique endpoint string with duration DSL.
+
+#### Non-Functional Validation
+
+After functional validation, check:
+
+- Template is in the correct folder, and filename matches `id`.
+- `id` is unique, descriptive, and uses 2-3 keywords (e.g., `alumni-management-sqli.yaml`). For CVE templates, the ID should be the CVE itself for example, CVE-2020-0796
+- `name` follows the format: `<Company> <Product> <Version> - <Vulnerability Class>` (e.g., `Adobe Coldfusion <=8.0.1 - Cross-Site Scripting`).
+- Fix capitalization, typos, or grammatical errors.
+- Update `tags`:
+  - Add vendor names (e.g., `Atlassian` for Jira/Confluence).
+  - Use `misconfig` for misconfigurations, `oss` for open-source CMS, `oast` for OAST templates, `intrusive` for file uploads or modifications.
+  - For CVEs, include `cve` and `cveYYYY` (e.g., `cve2022`).
+  - Tags should not contain spaces
+- Use `metadata` for additional info (e.g., `verified: true`, Shodan/FOFA queries).
+- Ensure proper `references` (e.g., WordPress plugin links, vendor pages).
+- Maintain consistent template structure and remove unnecessary headers/parameters.
+- Avoid using GET/POST data as matchers.
+- Fix indentation and trailing spaces using `yamllint` or the `validate` argument.
+- Assign a teammate for review before merging.
+
+#### Best Practices
+
+- For tech detection templates, consider adding templates for the tech’s panel or default credentials.
+- Ensure tag names start with the folder/vulnerability name.
+- Create a dedicated folder for technologies with multiple templates.
+- Add a `good first issue` label for first-time contributors’ PRs.
+- Use the `epic` label for creative templates.
+- Do not share vulnerable URLs publicly on GitHub or Discord.
+
+#### Below are examples of existing YAML templates for each protocol, along with their paths. You can use them as references when reviewing templates for the corresponding protocols.
+
+=== dast/vulnerabilities/ssti/oob/erb-erubi-erubis-oob.yaml ===
+```
+id: erb-erubi-erubis-oob
+
+info:
+  name: Erb OR Erubi OR Erubis - Out of Band Template Injection
+  author: 0xAwali,DhiyaneshDK
+  severity: high
+  reference:
+    - https://rubygems.org/gems/erb
+    - https://rubygems.org/gems/erubis
+    - https://medium.com/@0xAwali/template-engines-injection-101-4f2fe59e5756
+  metadata:
+    verified: true
+  tags: ssti,dast,oast,oob
+
+http:
+  - pre-condition:
+      - type: dsl
+        dsl:
+          - 'method == "GET"'
+
+    payloads:
+      injection:
+        - '<%25%3d(`nslookup+-type=SRV+{{interactsh-url}}`)%25>'
+
+    fuzzing:
+      - part: query
+        type: postfix
+        mode: single
+        fuzz:
+          - "{{injection}}"
+
+    matchers:
+      - type: dsl
+        name: request-matcher
+        dsl:
+          - "contains(interactsh_protocol,'dns')"
+          - "contains(interactsh_request,'srv')"
+        condition: and
+```
+
+=== http/vulnerabilities/nps/nps-auth-bypass.yaml ===
+```
+id: nps-auth-bypass
+
+info:
+  name: NPS - Authentication Bypass
+  author: SleepingBag945
+  severity: high
+  description: |
+    This will reveal all parameters configured on the NPS, including the account username and password of the proxy.
+  reference:
+    - https://mari0er.club/post/nps.html/
+  metadata:
+    verified: true
+    max-request: 1
+    shodan-query: html:"window.nps"
+  tags: nps,auth-bypass
+
+http:
+  - raw:
+      - |
+        POST /index/gettunnel HTTP/1.1
+        Host: {{Hostname}}
+        Content-Type: application/x-www-form-urlencoded
+
+        auth_key={{md5(unix_time())}}&timestamp={{unix_time()}}&offset=0&limit=10&type=socks5&client_id=&search=
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        part: body
+        words:
+          - '"VerifyKey":'
+          - 'Password":'
+          - 'Id":'
+        condition: and
+
+      - type: word
+        part: header
+        words:
+          - "application/json"
+
+      - type: status
+        status:
+          - 200
+```
+
+=== http/cves/2021/CVE-2021-41291.yaml ===
+```
+id: CVE-2021-41291
+
+info:
+  name: ECOA Building Automation System - Directory Traversal Content Disclosure
+  author: gy741
+  severity: high
+  description: The ECOA BAS controller suffers from a directory traversal content disclosure vulnerability. Using the GET parameter cpath in File Manager (fmangersub), attackers can disclose directory content on the affected device
+  impact: |
+    An attacker can exploit this vulnerability to access sensitive files and directories, potentially exposing sensitive information.
+  remediation: |
+    Apply the latest security patches or updates provided by the vendor to fix the directory traversal vulnerability in the ECOA Building Automation System.
+  reference:
+    - https://nvd.nist.gov/vuln/detail/CVE-2021-41291
+    - https://www.zeroscience.mk/en/vulnerabilities/ZSL-2021-5670.php
+    - https://www.twcert.org.tw/en/cp-139-5140-6343c-2.html
+    - https://www.twcert.org.tw/tw/cp-132-5127-3cbd3-1.html
+    - https://github.com/ARPSyndicate/cvemon
+  classification:
+    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
+    cvss-score: 7.5
+    cve-id: CVE-2021-41291
+    cwe-id: CWE-22
+    epss-score: 0.02626
+    epss-percentile: 0.90324
+    cpe: cpe:2.3:o:ecoa:ecs_router_controller-ecs_firmware:-:*:*:*:*:*:*:*
+  metadata:
+    max-request: 1
+    vendor: ecoa
+    product: ecs_router_controller-ecs_firmware
+  tags: cve,cve2021,ecoa,lfi,traversal
+
+http:
+  - raw:
+      - |
+        GET /fmangersub?cpath=../../../../../../../etc/passwd HTTP/1.1
+        Host: {{Hostname}}
+
+    matchers:
+      - type: regex
+        regex:
+          - "root:.*:0:0:"
+```
+
+=== code/windows/audit/minimum-password-age-zero.yaml ===
+```
+id: minimum-password-age-zero
+
+info:
+  name: Minimum Password Age Set to Zero
+  author: princechaddha
+  severity: medium
+  description: Checks if the minimum password age is set to zero, allowing immediate password changes and potential reuse.
+  impact: |
+    Allowing a password age of zero may lead to the rapid reuse of weak passwords, reducing account security.
+  remediation: |
+    Set a reasonable minimum password age to prevent users from reusing old passwords frequently.
+  tags: windows,password,policy,code,windows-audit
+
+self-contained: true
+
+code:
+  - pre-condition: |
+      IsWindows();
+    engine:
+      - cmd
+    args:
+      - /c
+    pattern: "*.cmd"
+    source: |
+      net accounts
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - "Minimum password age (days):                          0"
+        negative: true
+
+      - type: word
+        words:
+          - "Minimum password age"
+```
+
+=== cloud/azure/postgresql/azure-postgresql-storage-autogrow-disabled.yaml ===
+```
+id: azure-postgresql-storage-autogrow-disabled
+info:
+  name: Azure PostgreSQL Storage Auto-Growth Disabled
+  author: princechaddha
+  severity: high
+  description: |
+    Ensure that Storage Auto-Growth feature is enabled for your production Azure PostgreSQL database servers. Storage auto-growth prevents your PostgreSQL servers from running out of storage and becoming read-only.
+  impact: |
+    Failing to enable Storage Auto-Growth can lead to PostgreSQL servers running out of space, becoming read-only, and disrupting database services.
+  remediation: |
+    Enable the Storage Auto-Growth feature on your Azure PostgreSQL servers to prevent potential disruptions and ensure continuous database operation.
+  reference:
+    - https://docs.microsoft.com/en-us/azure/postgresql/concepts-storage
+  tags: cloud,devops,azure,microsoft,postgresql,azure-cloud-config
+
+flow: |
+  code(1);
+  for (let ServerData of iterate(template.serverList)) {
+    ServerData = JSON.parse(ServerData);
+    set("name", ServerData.Name);
+    set("resourceGroup", ServerData.ResourceGroup);
+    code(2);
+  }
+
+self-contained: true
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      az postgres server list --output json --query '[*].{"Name":name,"ResourceGroup":resourceGroup}'
+
+    extractors:
+      - type: json
+        name: serverList
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      az postgres server show --name "$name" --resource-group "$resourceGroup" --output json --query 'storageProfile.storageAutogrow'
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"Disabled"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'name + " in " + resourceGroup + " has Storage Auto-Growth disabled"'
+```
+
+=== ssl/c2/gozi-malware-c2.yaml ===
+```
+id: gozi-malware-c2
+
+info:
+  name: Gozi Malware C2 - Detect
+  author: pussycat0x
+  severity: info
+  description: |
+    Gozi is a banking Trojan that has been modified to include new obfuscation techniques, to evade detection. Previous breaches involving Gozi in the healthcare sector led to the compromise of data associated with 3.7 million patients costing $5.55 million.
+  reference: |
+    https://github.com/thehappydinoa/awesome-censys-queries#gozi-malware--
+  metadata:
+    verified: "true"
+    max-request: 1
+    censys-query: 'services.tls.certificates.leaf_data.issuer_dn: "C=XX, ST=1, L=1, O=1, OU=1, CN=\*"'
+  tags: ssl,tls,c2,ir,osint,malware,gozi
+ssl:
+  - address: "{{Host}}:{{Port}}"
+    matchers:
+      - type: word
+        part: issuer_dn
+        words:
+          - "CN=*, OU=1, O=1, L=1, ST=1, C=XX"
+
+    extractors:
+      - type: json
+        json:
+          - ".issuer_dn"
+```
+
+=== dns/mx-fingerprint.yaml ===
+```
+id: mx-fingerprint
+
+info:
+  name: MX Record Detection
+  author: pdteam
+  severity: info
+  description: An MX record was detected. MX records direct emails to a mail exchange server.
+  reference:
+    - https://www.cloudflare.com/learning/dns/dns-records/dns-mx-record/
+    - https://mxtoolbox.com/
+  classification:
+    cwe-id: CWE-200
+  metadata:
+    max-request: 1
+  tags: dns,mx
+
+dns:
+  - name: "{{FQDN}}"
+    type: MX
+    matchers:
+      - type: regex
+        part: answer
+        regex:
+          - "IN\tMX\\t(.+)$"
+
+    extractors:
+      - type: regex
+        group: 1
+        regex:
+          - "IN\tMX\t(.+)"
+```
+
+=== file/malware/shimrat-malware.yaml ===
+```
+id: shimrat-malware
+
+info:
+  name: ShimRat Malware - Detect
+  author: daffainfo
+  severity: info
+  reference: https://github.com/Yara-Rules/rules/blob/master/malware/RAT_Shim.yar
+  tags: malware,file
+file:
+  - extensions:
+      - all
+
+    matchers-condition: or
+    matchers:
+      - type: word
+        part: raw
+        words:
+          - ".dll"
+          - ".dat"
+          - "QWERTYUIOPLKJHG"
+          - "MNBVCXZLKJHGFDS"
+        condition: and
+
+      - type: word
+        part: raw
+        words:
+          - "Data$$00"
+          - "Data$$01%c%sData"
+        condition: and
+
+      - type: word
+        part: raw
+        words:
+          - "ping localhost -n 9 /c %s > nul"
+          - "Demo"
+          - "Win32App"
+          - "COMSPEC"
+          - "ShimMain"
+          - "NotifyShims"
+          - "GetHookAPIs"
+        condition: and
+```
+
+=== network/c2/7777botnet.yaml ===
+```
+id: 7777botnet-detect
+
+info:
+  name: 7777-Botnet - Detect
+  author: johnk3r
+  severity: info
+  reference:
+    - https://gi7w0rm.medium.com/the-curious-case-of-the-7777-botnet-86e3464c3ffd
+  metadata:
+    verified: true
+    max-request: 1
+    shodan-query: 'hash:1357418825'
+  tags: network,c2,ir,osint,cti,darktrack,botnet,tcp
+
+tcp:
+  - inputs:
+      - data: "fffc01fffb1ffffa1f00500018fff0fffd01fffd03"
+        read: 2048
+
+    host:
+      - "{{Hostname}}"
+    port: 7777
+
+    matchers:
+      - type: word
+        part: data
+        words:
+          - "xlog"
+          - "in"
+        condition: and
+```
+
+### Instructions for Comments
+
+Think step by step and structure your comments in two sections using GitHub Markdown:
+- Required Fixes – List missing or incorrect elements as a checklist (e.g., - [ ] Fix template ID to match filename).
+- Other Suggestions – Provide contextual recommendations, but only include suggestions you are 100% confident about.
@@ -44,6 +44,7 @@ Rewards are distributed once the template is fully validated. If the issue remai

 ## What should I include in my template submission?
 Include the following:
+> Avoid adding code templates for CVEs that can be achieved using HTTP, TCP, or JavaScript. Such templates are blocked by default and won’t produce results, so we prioritize creating templates with other protocols unless exceptions are made.
 - **Complete POC**: A working Proof of Concept.
 - **Matchers**: Multiple matchers to prevent false positives.
 - **Debug Data**: Data to assist the triage team in validation.
@@ -1,6 +1,6 @@
 MIT License

-Copyright (c) 2020 ProjectDiscovery, Inc.
+Copyright (c) 2025 ProjectDiscovery, Inc.

 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -42,18 +42,18 @@ An overview of the nuclei template project, including statistics on unique tags,

 |    TAG    | COUNT |    AUTHOR     | COUNT | DIRECTORY  | COUNT | SEVERITY | COUNT | TYPE | COUNT |
 |-----------|-------|---------------|-------|------------|-------|----------|-------|------|-------|
-| cve       |  2773 | dhiyaneshdk   |  1420 | http       |  8042 | info     |  3887 | file |   402 |
-| panel     |  1212 | daffainfo     |   866 | file       |   402 | high     |  2039 | dns  |    25 |
-| wordpress |  1046 | dwisiswant0   |   802 | cloud      |   325 | medium   |  1742 |      |       |
-| exposure  |   997 | princechaddha |   498 | workflows  |   192 | critical |  1158 |      |       |
-| xss       |   956 | ritikchaddha  |   455 | network    |   137 | low      |   280 |      |       |
-| wp-plugin |   915 | pussycat0x    |   452 | code       |    84 | unknown  |    43 |      |       |
-| osint     |   807 | pikpikcu      |   353 | javascript |    65 |          |       |      |       |
-| tech      |   729 | pdteam        |   302 | ssl        |    30 |          |       |      |       |
-| lfi       |   713 | ricardomaia   |   243 | dast       |    25 |          |       |      |       |
-| misconfig |   713 | geeknik       |   231 | dns        |    22 |          |       |      |       |
+| cve       |  3225 | dhiyaneshdk   |  1866 | http       |  8825 | info     |  4118 | file |   435 |
+| panel     |  1327 | daffainfo     |   868 | cloud      |   657 | high     |  2423 | dns  |    26 |
+| xss       |  1246 | dwisiswant0   |   806 | file       |   435 | medium   |  2339 |      |       |
+| wordpress |  1168 | princechaddha |   806 | dast       |   255 | critical |  1391 |      |       |
+| exposure  |  1094 | ritikchaddha  |   633 | workflows  |   202 | low      |   318 |      |       |
+| wp-plugin |  1023 | pussycat0x    |   519 | code       |   174 | unknown  |    54 |      |       |
+| osint     |   810 | pikpikcu      |   352 | network    |   141 |          |       |      |       |
+| tech      |   782 | pdteam        |   308 | javascript |    71 |          |       |      |       |
+| lfi       |   772 | pdresearch    |   251 | ssl        |    38 |          |       |      |       |
+| rce       |   770 | ricardomaia   |   249 | dns        |    23 |          |       |      |       |

-**723 directories, 9654 files**.
+**840 directories, 11171 files**.

 </td>
 </tr>
@@ -0,0 +1,99 @@
+
+
+<h1 align="center">
+Nuclei 模板
+</h1>
+<div align="center">
+<a href="README.md">English</a> |
+<a href="README_CN.md">简体中文</a> |
+<a href="README_JA.md">日本語</a> |
+<a href="README_KR.md">한국어</a>
+</div>
+<h4 align="center">这个仓库用于存放由社区精心挑选的模板,可以使用nuclei引擎结合模板发现应用中的漏洞。</h4>
+
+
+<p align="center">
+<a href="https://github.com/projectdiscovery/nuclei-templates/issues"><img src="https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat"></a>
+<a href="https://github.com/projectdiscovery/nuclei-templates/releases"><img src="https://img.shields.io/github/release/projectdiscovery/nuclei-templates"></a>
+<a href="https://twitter.com/pdnuclei"><img src="https://img.shields.io/twitter/follow/pdnuclei.svg?logo=twitter"></a>
+<a href="https://discord.gg/projectdiscovery"><img src="https://img.shields.io/discord/695645237418131507.svg?logo=discord"></a>
+</p>
+
+<p align="center">
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">文档</a> •
+  <a href="#-贡献">贡献</a> •
+  <a href="#-交流">交流</a> •
+  <a href="#-社区">社区</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
+  <a href="https://discord.gg/projectdiscovery">加入Discord</a>
+</p>
+
+----
+
+模板是 [nuclei 扫描器](https://github.com/projectdiscovery/nuclei) 的核心.
+这个git仓库储存了由PD团队以及社区贡献的各种扫描模板.
+我们希望您也能攻通过 **pull requests** 或者[Github issues](https://github.com/projectdiscovery/nuclei-templates/issues/new?assignees=&labels=&template=submit-template.md&title=%5Bnuclei-template%5D+)来提交模板以扩大我们的仓库列表.
+
+
+## Nuclei模板项目情况概述
+
+
+以下是nuclei模板项目的情况概览,包括唯一标签,作者,目录,严重性,模板类型的相关统计情况.以下表格列出了前面提到的每项情况的TOP10信息;你也可以点击[这里](TEMPLATES-STATS.md)查看详细信息.当然你也可以点击[这里](TEMPLATES-STATS.json)获取JSON格式的详细情况统计
+
+<table>
+<tr>
+<td> 
+
+## Nuclei模板TOP10统计信息
+
+|    TAG    | COUNT |    AUTHOR     | COUNT | DIRECTORY  | COUNT | SEVERITY | COUNT | TYPE | COUNT |
+|-----------|-------|---------------|-------|------------|-------|----------|-------|------|-------|
+| cve       |  2877 | dhiyaneshdk   |  1477 | http       |  8219 | info     |  3948 | file |   404 |
+| panel     |  1246 | daffainfo     |   866 | file       |   404 | high     |  2135 | dns  |    25 |
+| wordpress |  1072 | dwisiswant0   |   803 | cloud      |   370 | medium   |  1840 |      |       |
+| exposure  |  1006 | princechaddha |   570 | workflows  |   192 | critical |  1197 |      |       |
+| xss       |   987 | ritikchaddha  |   496 | code       |   157 | low      |   287 |      |       |
+| wp-plugin |   936 | pussycat0x    |   453 | network    |   138 | unknown  |    43 |      |       |
+| osint     |   807 | pikpikcu      |   353 | javascript |    65 |          |       |      |       |
+| tech      |   745 | pdteam        |   302 | ssl        |    30 |          |       |      |       |
+| lfi       |   727 | ricardomaia   |   245 | dast       |    26 |          |       |      |       |
+| misconfig |   720 | geeknik       |   231 | dns        |    22 |          |       |      |       |
+
+**743 directories, 9960 files**.
+
+</td>
+</tr>
+</table>
+
+📖 文档
+-----
+
+详细的文档请访问我们的网站[https://nuclei.projectdiscovery.io](https://nuclei.projectdiscovery.io),在我们网站的详细文档中,我们提供了如何创建模板的具体方法,并且也提供了相应的示例模板来帮助您更好地理解模板的开发以及运行原理.
+
+💪 贡献
+-----
+
+社区是Nuclei模板项目的主要贡献主力,我们非常欢迎开发者们来贡献模板,提出需求和报告Bug.
+
+![Alt](https://repobeats.axiom.co/api/embed/55ee65543bb9a0f9c797626c4e66d472a517d17c.svg "Repobeats analytics image")
+
+💬 交流
+-----
+
+如果您有任何关于该项目的疑问或是新奇的点子,欢迎在[Github discussions](https://github.com/projectdiscovery/nuclei-templates/discussions)创建新的板块来进行讨论.
+
+👨‍💻 社区
+-----
+
+欢迎您加入我们的[Discord 社区](https://discord.gg/projectdiscovery)，与项目维护人员直接讨论，或与其他人分享有关安全和自动化的想法。
+此外，您还可以在 [Twitter](https://twitter.com/pdnuclei) 上关注我们，了解 Nuclei 的最新动态。
+
+
+<p align="center">
+<a href="https://github.com/projectdiscovery/nuclei-templates/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=projectdiscovery/nuclei-templates&max=300">
+</a>
+</p>
+
+
+最后,感谢您对这个项目的贡献,这将让我们的社区更加充满活力.
@@ -1 +1 @@
-{"tags":[{"name":"cve","count":2773},{"name":"panel","count":1212},{"name":"wordpress","count":1046},{"name":"exposure","count":997},{"name":"xss","count":956},{"name":"wp-plugin","count":915},{"name":"osint","count":807},{"name":"tech","count":729},{"name":"lfi","count":713},{"name":"misconfig","count":713},{"name":"rce","count":659},{"name":"edb","count":598},{"name":"packetstorm","count":550},{"name":"wpscan","count":522},{"name":"cve2021","count":496},{"name":"cve2022","count":477},{"name":"wp","count":469},{"name":"cve2023","count":437},{"name":"sqli","count":415},{"name":"devops","count":403},{"name":"unauth","count":387},{"name":"detect","count":371},{"name":"authenticated","count":369},{"name":"cloud","count":360},{"name":"file","count":345},{"name":"intrusive","count":337},{"name":"login","count":337},{"name":"kev","count":282},{"name":"cve2024","count":270},{"name":"cve2020","count":257},{"name":"token-spray","count":246},{"name":"default-login","count":245},{"name":"oast","count":236},{"name":"microsoft","count":235},{"name":"top-200","count":229},{"name":"config","count":227},{"name":"apache","count":219},{"name":"malware","count":212},{"name":"osint-social","count":210},{"name":"azure","count":209},{"name":"network","count":202},{"name":"token","count":194},{"name":"","count":193},{"name":"azure-cloud-config","count":191},{"name":"cve2018","count":170},{"name":"iot","count":169},{"name":"cve2019","count":166},{"name":"install","count":160},{"name":"keys","count":156},{"name":"auth-bypass","count":150},{"name":"joomla","count":148},{"name":"redirect","count":146},{"name":"tcp","count":137},{"name":"aws","count":136},{"name":"ssrf","count":131},{"name":"amazon","count":118},{"name":"phishing","count":117},{"name":"cms","count":115},{"name":"files","count":114},{"name":"cve2017","count":114},{"name":"cve2010","count":112},{"name":"router","count":108},{"name":"top-100","count":100},{"name":"aws-cloud-config","count":91},{"name":"disclosure","count":90},{"name":"linux","count":85},{"name":"code","count":83},{"name":"seclists","count":82},{"name":"local","count":80},{"name":"takeover","count":79},{"name":"privesc","count":79},{"name":"tokens","count":78},{"name":"fileupload","count":76},{"name":"oracle","count":74},{"name":"kubernetes","count":73},{"name":"oss","count":71},{"name":"js","count":70},{"name":"cisco","count":70},{"name":"enum","count":65},{"name":"adobe","count":64},{"name":"ir","count":63},{"name":"k8s","count":62},{"name":"huntr","count":61},{"name":"cve2015","count":59},{"name":"atlassian","count":59},{"name":"vmware","count":57},{"name":"cve2016","count":57},{"name":"detection","count":57},{"name":"c2","count":57},{"name":"google","count":56},{"name":"tenable","count":49},{"name":"logs","count":48},{"name":"cve2014","count":48},{"name":"log4j","count":47},{"name":"vulhub","count":46},{"name":"debug","count":46},{"name":"hackerone","count":46},{"name":"php","count":46},{"name":"aem","count":45},{"name":"osint-gaming","count":45},{"name":"generic","count":45},{"name":"jndi","count":44},{"name":"deserialization","count":44},{"name":"cnvd","count":44},{"name":"traversal","count":43},{"name":"oa","count":43},{"name":"osint-porn","count":42},{"name":"osint-hobby","count":42},{"name":"plugin","count":42},{"name":"springboot","count":41},{"name":"misc","count":40},{"name":"injection","count":40},{"name":"miscellaneous","count":39},{"name":"ibm","count":39},{"name":"listing","count":39},{"name":"file-upload","count":38},{"name":"cti","count":37},{"name":"jira","count":37},{"name":"sap","count":35},{"name":"fuzz","count":35},{"name":"osint-misc","count":35},{"name":"k8s-cluster-security","count":34},{"name":"gitlab","count":33},{"name":"ssl","count":33},{"name":"dlink","count":32},{"name":"tls","count":32},{"name":"devsecops","count":32},{"name":"wp-theme","count":31},{"name":"osint-tech","count":31},{"name":"fortinet","count":31},{"name":"ec2","count":30},{"name":"osint-coding","count":30},{"name":"api","count":30},{"name":"lfr","count":28},{"name":"proxy","count":27},{"name":"bestwebsoft","count":27},{"name":"citrix","count":27},{"name":"dns","count":27},{"name":"info-leak","count":27},{"name":"tomcat","count":26},{"name":"firewall","count":26},{"name":"printer","count":26},{"name":"manageengine","count":26},{"name":"xxe","count":26},{"name":"ssh","count":26},{"name":"admin","count":26},{"name":"cve2012","count":26},{"name":"zohocorp","count":26},{"name":"dast","count":25},{"name":"zoho","count":25},{"name":"weaver","count":25},{"name":"prestashop","count":25},{"name":"osint-images","count":24},{"name":"osint-business","count":24},{"name":"osint-shopping","count":24},{"name":"osint-finance","count":24},{"name":"yonyou","count":24},{"name":"postgresql","count":24},{"name":"audit","count":23},{"name":"stored-xss","count":23},{"name":"cicd","count":23},{"name":"github","count":22},{"name":"s3","count":22},{"name":"dashboard","count":22},{"name":"msf","count":21},{"name":"ecology","count":21},Line truncated
+{"tags":[{"name":"cve","count":3225},{"name":"panel","count":1327},{"name":"xss","count":1246},{"name":"wordpress","count":1168},{"name":"exposure","count":1094},{"name":"wp-plugin","count":1023},{"name":"osint","count":810},{"name":"tech","count":782},{"name":"lfi","count":772},{"name":"rce","count":770},{"name":"misconfig","count":747},{"name":"devops","count":738},{"name":"cloud","count":697},{"name":"edb","count":599},{"name":"wp","count":573},{"name":"packetstorm","count":552},{"name":"wpscan","count":534},{"name":"cve2021","count":513},{"name":"cve2022","count":512},{"name":"cve2023","count":488},{"name":"detect","count":486},{"name":"sqli","count":484},{"name":"cve2024","count":462},{"name":"login","count":446},{"name":"unauth","count":431},{"name":"authenticated","count":422},{"name":"kev","count":405},{"name":"intrusive","count":398},{"name":"file","count":377},{"name":"oast","count":276},{"name":"default-login","count":275},{"name":"cve2020","count":274},{"name":"config","count":255},{"name":"token-spray","count":247},{"name":"apache","count":241},{"name":"microsoft","count":238},{"name":"top-200","count":235},{"name":"gcp","count":232},{"name":"gcp-cloud-config","count":226},{"name":"gcloud","count":224},{"name":"network","count":216},{"name":"malware","count":213},{"name":"token","count":211},{"name":"osint-social","count":210},{"name":"azure","count":210},{"name":"csp-bypass","count":204},{"name":"","count":204},{"name":"aws","count":192},{"name":"time-based-sqli","count":191},{"name":"azure-cloud-config","count":191},{"name":"iot","count":184},{"name":"cve2018","count":184},{"name":"auth-bypass","count":183},{"name":"cve2019","count":182},{"name":"amazon","count":175},{"name":"install","count":166},{"name":"code","count":157},{"name":"keys","count":156},{"name":"redirect","count":156},{"name":"joomla","count":151},{"name":"aws-cloud-config","count":147},{"name":"ssrf","count":144},{"name":"tcp","count":139},{"name":"security","count":133},{"name":"router","count":130},{"name":"files","count":125},{"name":"cms","count":123},{"name":"cve2017","count":119},{"name":"phishing","count":117},{"name":"cve2010","count":112},{"name":"kubernetes","count":111},{"name":"disclosure","count":107},{"name":"top-100","count":100},{"name":"tokens","count":97},{"name":"cve2025","count":94},{"name":"linux","count":88},{"name":"seclists","count":86},{"name":"oss","count":83},{"name":"takeover","count":81},{"name":"privesc","count":81},{"name":"local","count":81},{"name":"oracle","count":80},{"name":"fileupload","count":78},{"name":"js","count":75},{"name":"windows","count":74},{"name":"cisco","count":73},{"name":"enum","count":72},{"name":"k8s","count":71},{"name":"windows-audit","count":70},{"name":"adobe","count":65},{"name":"huntr","count":64},{"name":"ir","count":63},{"name":"alibaba","count":61},{"name":"cve2015","count":61},{"name":"cve2016","count":60},{"name":"file-upload","count":59},{"name":"detection","count":59},{"name":"atlassian","count":59},{"name":"google","count":57},{"name":"c2","count":57},{"name":"vmware","count":57},{"name":"audit","count":55},{"name":"deserialization","count":53},{"name":"dast","count":51},{"name":"cve2014","count":50},{"name":"php","count":50},{"name":"logs","count":50},{"name":"traversal","count":48},{"name":"hackerone","count":48},{"name":"log4j","count":48},{"name":"tenable","count":48},{"name":"ssh","count":47},{"name":"generic","count":47},{"name":"debug","count":47},{"name":"vulhub","count":46},{"name":"misc","count":46},{"name":"ssti","count":46},{"name":"cnvd","count":46},{"name":"aem","count":46},{"name":"osint-gaming","count":45},{"name":"aliyun","count":45},{"name":"injection","count":45},{"name":"jndi","count":44},{"name":"plugin","count":44},{"name":"ssl","count":43},{"name":"springboot","count":43},{"name":"oa","count":43},{"name":"osint-porn","count":42},{"name":"osint-hobby","count":42},{"name":"fortinet","count":42},{"name":"ibm","count":42},{"name":"firewall","count":41},{"name":"tls","count":41},{"name":"listing","count":40},{"name":"miscellaneous","count":39},{"name":"dlink","count":39},{"name":"info-leak","count":39},{"name":"postgresql","count":39},{"name":"sap","count":38},{"name":"k8s-cluster-security","count":37},{"name":"jira","count":37},{"name":"cti","count":37},{"name":"api","count":37},{"name":"wp-theme","count":36},{"name":"google-cloud-sql","count":36},{"name":"osint-misc","count":35},{"name":"networking","count":34},{"name":"devsecops","count":34},{"name":"gitlab","count":34},{"name":"lfr","count":34},{"name":"xxe","count":33},{"name":"fuzz","count":33},{"name":"dns","count":32},{"name":"nginx","count":31},{"name":"vpc","count":31},{"name":"printer","count":31},{"name":"osint-tech","count":31},{"name":"osint-coding","count":30},{"name":"alibaba-cloud-config","count":30},{"name":"ec2","count":30},{"name":"admin","count":29},{"name":"gke","count":29},{"name":"prestashop","count":29},{"name":"tomcat","count":28},{"name":"proxy","count":28},{"namLine truncated
@@ -1,12 +1,12 @@
 |    TAG    | COUNT |    AUTHOR     | COUNT | DIRECTORY  | COUNT | SEVERITY | COUNT | TYPE | COUNT |
 |-----------|-------|---------------|-------|------------|-------|----------|-------|------|-------|
-| cve       |  2773 | dhiyaneshdk   |  1420 | http       |  8042 | info     |  3887 | file |   402 |
-| panel     |  1212 | daffainfo     |   866 | file       |   402 | high     |  2039 | dns  |    25 |
-| wordpress |  1046 | dwisiswant0   |   802 | cloud      |   325 | medium   |  1742 |      |       |
-| exposure  |   997 | princechaddha |   498 | workflows  |   192 | critical |  1158 |      |       |
-| xss       |   956 | ritikchaddha  |   455 | network    |   137 | low      |   280 |      |       |
-| wp-plugin |   915 | pussycat0x    |   452 | code       |    84 | unknown  |    43 |      |       |
-| osint     |   807 | pikpikcu      |   353 | javascript |    65 |          |       |      |       |
-| tech      |   729 | pdteam        |   302 | ssl        |    30 |          |       |      |       |
-| lfi       |   713 | ricardomaia   |   243 | dast       |    25 |          |       |      |       |
-| misconfig |   713 | geeknik       |   231 | dns        |    22 |          |       |      |       |
+| cve       |  3225 | dhiyaneshdk   |  1866 | http       |  8825 | info     |  4118 | file |   435 |
+| panel     |  1327 | daffainfo     |   868 | cloud      |   657 | high     |  2423 | dns  |    26 |
+| xss       |  1246 | dwisiswant0   |   806 | file       |   435 | medium   |  2339 |      |       |
+| wordpress |  1168 | princechaddha |   806 | dast       |   255 | critical |  1391 |      |       |
+| exposure  |  1094 | ritikchaddha  |   633 | workflows  |   202 | low      |   318 |      |       |
+| wp-plugin |  1023 | pussycat0x    |   519 | code       |   174 | unknown  |    54 |      |       |
+| osint     |   810 | pikpikcu      |   352 | network    |   141 |          |       |      |       |
+| tech      |   782 | pdteam        |   308 | javascript |    71 |          |       |      |       |
+| lfi       |   772 | pdresearch    |   251 | ssl        |    38 |          |       |      |       |
+| rce       |   770 | ricardomaia   |   249 | dns        |    23 |          |       |      |       |
@@ -0,0 +1,39 @@
+id: ack-cluster-api-public
+
+info:
+  name: Public Access to ACK Cluster's API Server - Enabled
+  author: ritikchaddha
+  severity: high
+  description: |
+    Ensure that your ACK cluster's API server is not publicly accessible in order to avoid exposing private data and minimizing security risks. The level of access to your Kubernetes API server depends on your application use cases, however, for most use cases, the Kubernetes API Server should be accessible only from within your Virtual Private Cloud (VPC).
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/private-cluster.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - 'master_url":'
+          - 'api_server_endpoint\":\"'
+
+      - type: word
+        words:
+          - 'api_server_endpoint\":\"\",'
+        negative: true
+# digest: 4b0a00483046022100b7fc429fd01243451efc9c2af29a4f7dd9fa7d3d472f6b2390b237f52c8d29bd022100e7e94a2b747bfaf80f269494c33d26ad15655c94116df0673fc9002d46206901:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,57 @@
+id: ack-cluster-auditing-disable
+
+info:
+  name: Cluster Auditing with Simple Log Service - Disabled
+  author: ritikchaddha
+  severity: low
+  description: |
+    Ensure that cluster auditing with Simple Log Service is enabled for your Container Service for Kubernetes (ACK) clusters. Simple Log Service is a comprehensive real-time data logging solution, facilitating the seamless handling of log collection, shipping, search, storage, and analysis. The service provides a user-friendly interface for accessing the Log Viewer and an API for efficient log management. Simple Log Service automatically captures, processes, and stores container and audit logs in a dedicated persistent datastore, collecting container logs from your containers and audit logs from kube-apiserver or deployed ingress, including cluster activity events.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/enable-log-service.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let cluster_id of iterate(template.cluster)) {
+    set("cluster", cluster_id)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    extractors:
+      - type: json
+        name: cluster
+        internal: true
+        json:
+          - '.[].cluster_id'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters/$cluster --header "Content-Type=application/json;" --body "{}" --output cols=meta_data
+
+    matchers:
+      - type: regex
+        regex:
+          - '"AuditProjectName"\s*:\s*""'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'cluster + " Cluster auditing with Simple Log Service is not enabled"'
+# digest: 4a0a004730450220160df17dd98b2a12cee21ca6be28a84bf07a320c50059dd0513c0423203a3695022100b87631bebd1d69e7e6aa109c74ceb89f5c22358ee5bf1643a4f67e6986447559:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: ack-cluster-cloud-monitor-disable
+
+info:
+  name: Cloud Monitor for ACK Clusters - Disable
+  author: ritikchaddha
+  severity: medium
+  description: |
+    Ensure that Cloud Monitor is enabled for your Container Service for Kubernetes (ACK) clusters. Cloud Monitor relies on a specialized agent for accessing extra system resources and application services within virtual machine instances. The agent allows monitoring of metrics such as CPU utilization, specific disk traffic metrics, network traffic, and disk IO information. These metrics play a crucial role in observing signals and facilitating operational activities within your Kubernetes Engine clusters.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/enable-cloud-monitor.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let cluster_id of iterate(template.cluster)) {
+    set("cluster", cluster_id)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    extractors:
+      - type: json
+        name: cluster
+        internal: true
+        json:
+          - '.[].cluster_id'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters/$cluster/nodepools --header "Content-Type=application/json;" --body "{}"
+
+    matchers:
+      - type: word
+        words:
+          - 'kubernetes_config":'
+          - 'cms_enabled": false'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'cluster + " Cloud Monitor service is not enabled"'
+# digest: 4a0a00473045022069baf44dc8c97e8026d54120e12b42a8b2b357a2dd490006b00d89291f18aebb022100e75b0f9abc1083ab553db314b51fba7ba3f51c66a2556c7f4a8d78b8270747dc:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,64 @@
+id: ack-cluster-health-disable
+
+info:
+  name: ACK Clusters Check - Disable
+  author: ritikchaddha
+  severity: medium
+  description: |
+    Ensure that the Cluster Check feature is triggered at least once per week to guarantee proactive health monitoring for your ACK clusters, minimizing downtime and optimizing the reliability of your containerized applications. By default, Cluster Check is not automatically triggered, the cluster inspection can be started using the Container Service for Kubernetes (ACK) console.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/cluster-check.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let cluster_id of iterate(template.cluster)) {
+    set("cluster", cluster_id)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    extractors:
+      - type: json
+        name: cluster
+        internal: true
+        json:
+          - '.[].cluster_id'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters/$cluster/checks --header "Content-Type=application/json;" --body "{}"
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - 'check_id":'
+          - 'status":'
+
+      - type: word
+        words:
+          - '"status": "Succeeded'
+        negative: true
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'cluster + " Cluster Health Check is Disabled"'
+# digest: 4a0a00473045022100ea949f6a65a4168fdcd3d79fea251acf2f4459e93dfade94b797f1c102c5396802204af0738eaf3419762f4832983c36e39a459e21ef1551b0b17a3a15c81e404d0c:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,63 @@
+id: ack-cluster-network-policies-disable
+
+info:
+  name: Enforced Cluster Support for Network Policies - Disabled
+  author: ritikchaddha
+  severity: medium
+  description: |
+    Ensure that your ACK clusters are using Kubernetes network policies to implement secure policy-based access control. Container Service for Kubernetes (ACK) employs the Terway network plugin to enforce network policies at the cluster level.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/enable-network-policy-support.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let cluster_id of iterate(template.cluster)) {
+    set("cluster", cluster_id)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    matchers:
+      - type: word
+        words:
+          - '"Network": "terway-eniip"'
+        internal: true
+
+    extractors:
+      - type: json
+        name: cluster
+        internal: true
+        json:
+          - '.[].cluster_id'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters/$cluster --header "Content-Type=application/json;" --body "{}" --output cols=meta_data
+
+    matchers:
+      - type: word
+        words:
+          - 'NetworkPolicy\":\"false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'cluster + " Cluster is not using the plugin to enforce network policies"'
+# digest: 490a004630440220640da8dee3686d45b8d38d62d63cf5d7449b99340f644d1095463046e03db60602204eb932c45b8397a18c4562f067d09bd397bf4ddd06c5efeed9d66fc82f681f19:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,43 @@
+id: ack-cluster-network-policies-missing
+
+info:
+  name: Cluster Support for Network Policies - Missing
+  author: ritikchaddha
+  severity: medium
+  description: |
+    Ensure that your ACK clusters are using Kubernetes network policies to implement secure policy-based access control. Container Service for Kubernetes (ACK) employs the Terway network plugin to enforce network policies at the cluster level.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/enable-network-policy-support.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    matchers-condition: and
+    matchers:
+      - type: regex
+        regex:
+          - '"Network"\s*:\s*"'
+
+      - type: word
+        words:
+          - '"Network": "terway-eniip"'
+        negative: true
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"Cluster is not using the plugin to enforce network policies"'
+# digest: 490a004630440220131fa00233007ecfe8f70fc500b4efa66999ba6f1eb7d2987484c56ef13075dc02203e74e8da876a147c37d6de2a89c5995d52ca2933f9ec2eb473122fe32656a198:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,57 @@
+id: kubernetes-dashboard-enabled
+
+info:
+  name: Kubernetes Dashboard for ACK Clusters - Enabled
+  author: ritikchaddha
+  severity: medium
+  description: |
+    Ensure that Kubernetes Dashboard (Dashboard WebUI) is disabled for your ACK clusters in order to enhance cluster security and prevent potential attack vectors. The Kubernetes Dashboard is a web-based user interface (UI) that provides a visual representation and management capabilities for Kubernetes clusters. It allows users to monitor and interact with the resources within the cluster, such as pods, deployments, and services, through a graphical interface rather than using command-line tools.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ACK/disable-kubernetes-dashboard.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ack
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let cluster_id of iterate(template.cluster)) {
+    set("cluster", cluster_id)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs GET /clusters --header "Content-Type=application/json;" --body "{}"
+
+    extractors:
+      - type: json
+        name: cluster
+        internal: true
+        json:
+          - '.[].cluster_id'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun cs DescribeClusterAddonsVersion --ClusterId $cluster
+
+    matchers:
+      - type: word
+        words:
+          - 'kubernetes-dashboard'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'cluster + " Kubernetes Dashboard is enabled for the selected ACK cluster"'
+# digest: 4b0a00483046022100b4f98ba55922b99ffbf57dd68fa814f198dd99130e9d1d6c168a246eb842d3260221009a8c004329b2015cefef39ffbb2c7abda163de2e0d00132796e1cc133d5a5531:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,45 @@
+id: multi-region-logging-disabled
+
+info:
+  name: Global Service (Multi-Region) Logging - Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    Global Service (Multi-Region) Logging is disabled, preventing the collection and monitoring of logs across multiple regions. This lack of centralized logging increases the risk of undetected security incidents and operational issues.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ActionTrail/enable-multi-region-trails.html
+    - https://www.alibabacloud.com/help/en/actiontrail/product-overview/services-that-work-with-actiontrail
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,actiontrail
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun actiontrail DescribeTrails --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"TrailRegion": "All"'
+        negative: true
+
+      - type: word
+        words:
+          - '"Status": "Enable"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"ActionTrail for Global Service Multi-Region is Disabled "'
+# digest: 4a0a0047304502200d2f4254879df34c1ea310e2004cbf0aeaecf7c33a55250b548ecd6647e58b0a022100e8d4c5c83d25132dc839a5035cff3ee4b21130b0801b9ecfaca6f3fe26b9ea08:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,57 @@
+id: public-actiontrail-bucket
+
+info:
+  name: ActionTrail Log Buckets - Publicly Exposed
+  author: ritikchaddha
+  severity: high
+  description: |
+    Identify any publicly accessible ActionTrail trail log buckets in order to determine if your Alibaba Cloud account could be at risk. A publicly accessible trail bucket is a bucket were all users, including anonymous users, can perform read and write operations on the objects within the bucket.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ActionTrail/trail-bucket-publicly-accessible.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,actiontrail
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun actiontrail DescribeTrails --region $region
+
+    extractors:
+      - type: json
+        name: bucketname
+        internal: true
+        json:
+          - '.TrailList[].OssBucketName'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil stat oss://$bucket
+
+    matchers:
+      - type: regex
+        regex:
+          - 'ACL.*:.*public-read-write'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'bucket + " Bucket associated with ActionTrail trail is publicly accessible"'
+# digest: 4b0a004830460221009ad0983bbbc67aceaeefae2e0f2f98390937e979ed51482d79b61c41c11d662602210098b877f52c1cf1cc3273194270ad3d4dbdd9f07b50237fb110adcce97771bb0c:41987585204b393149694b2205534b1a
@@ -0,0 +1,69 @@
+id: alibaba-cloud-code-env
+
+info:
+  name: Alibaba Cloud Environment Validation
+  author: DhiyaneshDK
+  severity: info
+  description: |
+    Checks if Aliyun CLI is set up and all necessary tools are installed on the environment.
+  reference:
+    - https://github.com/aliyun/aliyun-cli
+  metadata:
+    max-request: 3
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config
+
+variables:
+  region: "cn-hangzhou"
+
+flow: code(1) && code(2) && code (3)
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun sts GetCallerIdentity
+
+    matchers:
+      - type: word
+        internal: true
+        words:
+          - '"UserId":'
+
+    extractors:
+      - type: json
+        name: account
+        internal: true
+        json:
+          - '.AccountId'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      jq --version >/dev/null 2>&1 && echo "jq is installed." || echo "jq is not installed."
+
+    matchers:
+      - type: word
+        words:
+          - "jq is installed"
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil --version >/dev/null 2>&1 && echo "ossutil is installed." || echo "ossutil is not installed."
+
+    matchers:
+      - type: word
+        words:
+          - "ossutil is installed"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"Aliyun CLI is properly configured for account \"" + account + "\" and all the necessary tools required are installed."'
+# digest: 4a0a0047304502201c12ee70fb96893100a7ac8999e01834ac017716a0cdf13249855690a2c096a70221008644bea38cae55a580d6f044fd2b944e416d9f13ab32c1662a1c30cd60542014:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,48 @@
+id: os-patches-outdated
+
+info:
+  name: OS Patches - Outdated
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that the latest OS patches for ECS virtual machines (VM) instances are applied in order to mitigate security vulnerabilities and ensure optimal performance and stability.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ECS/apply-latest-os-patches.html
+    - https://www.alibabacloud.com/help/en/security-center/user-guide/fix-software-vulnerabilities
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,ecs
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun sas DescribeVulList --Type cve --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"RaspStatus":'
+          - '"Type":'
+        condition: and
+
+      - type: word
+        words:
+          - '"TotalCount": 0'
+          - '"VulRecords":'
+        condition: and
+        negative: true
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '" OS Patches are Outdated "'
+# digest: 490a004630440220075d428a4f7bf677cfb89468182e7f1e917c233bd6df02a9df3e0bc705434aa502204af7cc4cfcff4b1cbdb9b876b678b263a1486cbb328c2045cd209970f6221e3a:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,38 @@
+id: unattached-disk-encryption-disabled
+
+info:
+  name: Encryption for Unattached Disks - Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    Unencrypted unattached disks in Alibaba Cloud pose a risk of data exposure if accessed by unauthorized users. Enabling encryption ensures the security of sensitive data at rest.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ECS/encrypt-unattached-disks.html
+    - https://www.alibabacloud.com/help/en/ecs/user-guide/encrypt-a-data-disk
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,ecs
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ecs DescribeDisks --Status Available --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"Encrypted": false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '" Encryption for Unattached Disks is Disabled "'
+# digest: 4a0a00473045022100e3f1eb9d2f25397e2c3f9b1fc03ff807b1f188d0168bd3bb3f37314a23a68d6f02200a78f4cbcbf9c402d5e827134acfe497858577368c7c4ee8792fd1cd97198c32:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,66 @@
+id: unattached-vminstance-encryption-disabled
+
+info:
+  name: Encryption for VM Instance Disks - Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    The encryption for VM instance disks in Alibaba Cloud is currently disabled. This means that the data stored on these disks is not automatically encrypted for enhanced security.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ECS/encrypt-vm-instance-disks.html
+    - https://www.alibabacloud.com/help/en/ecs/user-guide/encrypt-a-system-disk
+    - https://www.alibabacloud.com/help/en/ecs/user-guide/encrypt-a-data-disk
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,ecs
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let InstanceId of iterate(template.instanceid)){
+    set("instanceid", InstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ecs DescribeDisks --region $region
+
+    extractors:
+      - type: json
+        name: instanceid
+        internal: true
+        json:
+          - '.Disks.Disk[].InstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ecs DescribeDisks --InstanceId $instanceid --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"Encrypted": false'
+
+      - type: word
+        words:
+          - '"InstanceId": ""'
+        negative: true
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instanceid + " Encryption for VM Instance Disks is Disabled"'
+# digest: 490a00463044022065fc7c09f5a02fdbe644ceaf7fa05f05cc3ef357da65955c28917e0e7f18911c02205ff663b81f41ec4df06ecdaf43243c0b903c4971aca650730e6d51c918037c11:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,62 @@
+id: unrestricted-rdp-access
+
+info:
+  name: Unrestricted - RDP Access
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    Unrestricted RDP (Remote Desktop Protocol) access allows anyone on the internet to attempt to connect to your instance using port 3389, which is commonly used for RDP. This can expose the instance to potential brute force attacks, unauthorized access attempts, and exploitation of vulnerabilities in the RDP service.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ECS/unrestricted-rdp-access.html
+    - https://www.alibabacloud.com/help/en/ecs/use-cases/best-practices-of-the-security-group
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,ecs
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let SecurityGroupId of iterate(template.securitygroup)){
+    set("securitygroup", SecurityGroupId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ecs DescribeSecurityGroups --RegionId $region
+
+    extractors:
+      - type: json
+        name: securitygroup
+        internal: true
+        json:
+          - '.SecurityGroups.SecurityGroup[].SecurityGroupId'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ecs DescribeSecurityGroupAttribute --SecurityGroupId "$securitygroup" --Direction ingress --RegionId $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"IpProtocol": "TCP"'
+          - '"PortRange": "3389/3389"'
+          - '"SourceCidrIp": "0.0.0.0/0"'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'securitygroup + " contains Unrestricted RDP Access"'
+# digest: 4b0a0048304602210083f03472a0f1275e78b08fc4b68bde30bca25b86d874e0b7f53691e7259a9574022100aff7788972912f8e416e28adb1e05a94f601b3c5904ac26e5ad79f69ed46cc39:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,62 @@
+id: unrestricted-ssh-access
+
+info:
+  name: Unrestricted - SSH Access
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    Unrestricted SSH access allows anyone on the internet to attempt connections to your instance over port 22, posing a risk of brute force attacks, unauthorized access, and exploitation of SSH vulnerabilities. Limiting access to trusted IPs is essential to secure your instance.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-ECS/unrestricted-ssh-access.html
+    - https://www.alibabacloud.com/help/en/ecs/use-cases/best-practices-of-the-security-group
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,ecs
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let SecurityGroupId of iterate(template.securitygroup)){
+    set("securitygroup", SecurityGroupId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ecs DescribeSecurityGroups --RegionId $region
+
+    extractors:
+      - type: json
+        name: securitygroup
+        internal: true
+        json:
+          - '.SecurityGroups.SecurityGroup[].SecurityGroupId'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ecs DescribeSecurityGroupAttribute --SecurityGroupId "$securitygroup" --Direction ingress --RegionId $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"IpProtocol": "TCP"'
+          - '"PortRange": "22/22"'
+          - '"SourceCidrIp": "0.0.0.0/0"'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'securitygroup + " contains Unrestricted SSH Access"'
+# digest: 4a0a00473045022078d2940e35439fb3d9447ac4fe8aa08ec376448ea3458f938bdbf7159089aa8c022100f9751047f3976afb22ed1b7db9d481f2cee00cfe1513dcc4e53818e0df7451c7:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,63 @@
+id: access-logoss-disabled
+
+info:
+  name: Access Logging for OSS Buckets - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Disabling access logging for OSS buckets reduces the ability to monitor and audit access, increasing the risk of undetected unauthorized activity.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/enable-bucket-access-logging.html
+    - https://www.alibabacloud.com/help/en/oss/user-guide/getting-started
+    - https://www.alibabacloud.com/help/en/oss/user-guide/enable-logging
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,alibaba-oss
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss ls --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss logging --method get $bucket --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '<LoggingEnabled>'
+          - '<TargetBucket></TargetBucket>'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'bucket + " Access Logging for OSS Buckets is Disabled "'
+# digest: 490a0046304402202c7db531327c5aa97814ff449d8796b0520264e13d531fcebdf3e90d64252cb60220045d1db959712237219b389022dbaabf1bcb023ca5151e5539546aad2819d8c7:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,58 @@
+id: improper-bucket-sse
+
+info:
+  name: Improper Bucket Server-Side Encryption
+  author: ritikchaddha
+  severity: medium
+  description: |
+    Determine the Server-Side Encryption (SSE) feature configuration available for the selected OSS bucket. For compliance, the SSEAlgorithm must be set to KMS.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/enable-sse-with-customer-managed-key.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,oss
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil ls -s --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil bucket-encryption --method get $bucket
+
+    matchers:
+      - type: regex
+        regex:
+          - 'SSEAlgorithm:\s?AES256'
+          - 'StatusCode=404'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'bucket + " Bucket SSEAlgorithm is not set to KMS"'
+# digest: 490a0046304402205bdf1095c23f74d8032d8c8ed10841cd2574f186f2d0a7e6a8b484974f0079c30220378a0a9868705810364cd850515e1f5a63b7596aef948a1a65372871462b69a6:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,70 @@
+id: limit-networkaccess-disabled
+
+info:
+  name: Limit Network Access to Selected Networks - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Limit Network Access to Selected Networks in Alibaba OSS allows you to restrict access to your object storage service (OSS) to specific IP addresses or IP ranges, enhancing security by ensuring that only trusted networks can interact with your data."
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/publicly-accessible-oss-bucket.html
+    - https://www.alibabacloud.com/help/en/oss/user-guide/block-public-access
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,alibaba-oss
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss ls --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss bucket-policy --method get $bucket --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"IpAddress":'
+          - '"acs:SourceIp":'
+        negative: true
+
+      - type: word
+        words:
+          - '"Principal":'
+          - '"Resource":'
+          - '"Action":'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'bucket + " Limit Network Access to Selected Networks is Disabled "'
+# digest: 4a0a0047304502207e35a18d8164528de48029765a8fe55797af61fff934bb5d0b18d47fed41ae9a022100fab60e8b59b6a61f40ea8a69ca9b3e268c81ece8809a37425fc72b11ac7bc5ac:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,68 @@
+id: oos-bucket-public-access
+
+info:
+  name: OSS Bucket Public Accessible
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    Ensure that your Object Storage Service (OSS) buckets are not publicly accessible to the Internet in order to protect against unauthorized access. Allowing public, anonymous access through bucket ACLs and bucket policies gives everyone the ability to access bucket contents.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/publicly-accessible-oss-bucket.html
+    - https://www.alibabacloud.com/help/en/oss/user-guide/block-public-access
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,alibaba-oss
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss ls --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss stat $bucket --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - 'private'
+        negative: true
+
+      - type: word
+        words:
+          - 'public-read'
+          - 'public-read-write'
+        condition: or
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'bucket + " OSS Bucket is Public Accessible "'
+# digest: 4b0a00483046022100ebe3f235d7b322069926037bb46627b158f4c3aaef6fce8f53d5b7796c00d1f6022100a423932d5a987382196d74de46a97ba1dcb4b25980a28181945ee69c70512e45:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,68 @@
+id: secure-transfeross-disabled
+
+info:
+  name: Secure Transfer for OSS Buckets - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Disabling secure transfer (HTTPS) for OSS buckets exposes data to potential interception. It is recommended to enable HTTPS to ensure encrypted communication and data security.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/enable-secure-transfer.html
+    - https://www.alibabacloud.com/help/en/oss/user-guide/use-bucket-policy-to-grant-permission-to-access-oss/
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,alibaba-oss
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss ls --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun oss bucket-policy --method get $bucket --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '"acs:SecureTransport":'
+        negative: true
+
+      - type: word
+        words:
+          - '"Resource":'
+          - '"Principal":'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'bucket + " Secure Transfer for OSS Buckets "'
+# digest: 490a0046304402205263fc71592240b51cc863e754efcf1a93e92cc10fa959cceb7c060facf15380022062ca3fc3027d327ed1902e208f39a88b57e8023b1869dcad5588940663145872:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,76 @@
+id: sse-cmk-disabled
+
+info:
+  name: Server-Side Encryption with Customer Managed Key - Disabled
+  author: ritikchaddha
+  severity: high
+  description: |
+    Ensure that Server-Side Encryption (SSE) is using customer-managed keys (CMKs) instead of service-managed keys to protect your OSS data at rest. SSE with customer-managed keys (also known as Bring Your Own Key - BYOK) enables you to have full control over the encryption and decryption process and meet strict compliance requirements.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/enable-sse-with-customer-managed-key.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,ecs
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+    for (let KMSMasterKeyID of iterate(template.KmsID)) {
+      set("KmsID", KMSMasterKeyID)
+      code(3)
+    }
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil ls -s --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil bucket-encryption --method get $bucket --RegionId $region
+
+    extractors:
+      - type: regex
+        name: KmsID
+        internal: true
+        regex:
+          - 'KMSMasterKeyID: ([a-z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun kms DescribeKey --KeyId $KmsID --RegionId $region
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - 'Creator": "Rds'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'KmsID + " SSE with customer-managed keys Disable"'
+# digest: 4b0a00483046022100b066e8817becee38cb2b4857e6b84c939bb4cc9db6dae5efa90543d3c1becd57022100ecf71b3ad8d9d15f7eecc8f24441926de5d67b184ca58119e77fb12add36bfe2:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,75 @@
+id: sse-smk-disabled
+
+info:
+  name: Server-Side Encryption with Service Managed Key - Disabled
+  author: ritikchaddha
+  severity: high
+  description: |
+    Ensure that Server-Side Encryption (SSE) is using customer-managed keys (CMKs) instead of service-managed keys to protect your OSS data at rest. SSE with customer-managed keys (also known as Bring Your Own Key - BYOK) enables you to have full control over the encryption and decryption process and meet strict compliance requirements.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-OSS/enable-sse-with-service-key.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,aliyun-cloud-config,oss
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for (let BucketName of iterate(template.bucketname)) {
+    set("bucket", BucketName)
+    code(2)
+    for (let KMSMasterKeyID of iterate(template.KmsID)) {
+      set("KmsID", KMSMasterKeyID)
+      code(3)
+    }
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil ls -s --region $region
+
+    extractors:
+      - type: regex
+        name: bucketname
+        internal: true
+        regex:
+          - 'oss://([a-zA-Z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      ossutil bucket-encryption --method get $bucket
+
+    extractors:
+      - type: regex
+        name: KmsID
+        internal: true
+        regex:
+          - 'KMSMasterKeyID: ([a-z0-9-]+)'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun kms ListAliasesByKeyId --KeyId $KmsID
+
+    matchers:
+      - type: word
+        words:
+          - 'AliasName": "alias/acs/rds'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'KmsID + " SSE with service-managed key Disable"'
+# digest: 490a0046304402201f11561ccac93c5f9c3f01b039ab732fcda5bd2fbea367d3f69e40a2116e2e9d022072c6621d2ee39c602af009b2127eaf59b7fbb7d03a39843c98636bcdd61592b6:41987585204b393149694b2205534b1a
@@ -0,0 +1,64 @@
+id: custom-ram-policy-admin-priv
+
+info:
+  name: Custom RAM Policies With Full Administrative Privileges
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    The Alibaba Cloud Custom RAM policies with full administrative privileges grant users or groups unrestricted access to all resources and actions within the cloud environment.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/create-a-custom-policy
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/policies-with-full-administrative-privileges.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let PolicyName of iterate(template.policyname)){
+    set("policy", PolicyName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ram ListPolicies --PolicyType Custom --region $region
+
+    extractors:
+      - type: json
+        name: policyname
+        internal: true
+        json:
+          - '.Policies.Policy[].PolicyName'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ram GetPolicy --PolicyName $policyname --PolicyType Custom --region $region
+
+
+    matchers:
+      - type: word
+        words:
+          - '"Effect\":\"Allow\'
+          - '\"Action\":\"*\"'
+          - '\"Resource\":\"*\"'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'policy + " custom RAM Policy allow Full Administrative Privileges "'
+# digest: 4a0a0047304502204cbc305a46f0716c1d9cde8d2e7eb3267ea7b1d03724236860e6bbb6e75ce077022100c4f3830e4b2e5d3f63b7f68d5fbd35792e74fb3f0faebb0f9b05877ff71dfb21:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,38 @@
+id: max-password-retry-disabled
+
+info:
+  name: Maximum Password Retry Constraint Policy - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The password retry constraint policy for RAM (Resource Access Management) users in Alibaba Cloud is either disabled or not properly configured
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"MaxLoginAttemps": 0'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"Maximum Password Retry Constraint Policy is Disabled "'
+# digest: 4a0a00473045022100f3433183b0212970a977499997f3e2c24d64c9450e10fd8b08ee4c813be0bb5c02202782c8d0ddf2c2bd5f715a11f3561d0635cb7d5994439495302e4b5936e38054:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,60 @@
+id: mfa-console-password-disabled
+
+info:
+  name: MFA For RAM Users With Console Password - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    MFA (Multi-Factor Authentication) for RAM users with console password is currently disabled, meaning users can access the console without requiring a second form of authentication. This configuration reduces security by not enforcing an additional layer of protection beyond the password.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/bind-an-mfa-device-to-a-ram-user
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/ram-user-multi-factor-authentication-enabled.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let UserName of iterate(template.username)){
+    set("user", UserName)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ram ListUsers --region $region
+
+    extractors:
+      - type: json
+        name: username
+        internal: true
+        json:
+          - '.Users.User[].UserName'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ram GetLoginProfile --UserName $user --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"MFABindRequired": false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'username + "MFA For RAM Users With Console Password is Disabled "'
+# digest: 4b0a00483046022100c7afcb5e2dc6dc985fe7cdacc0c4b9df46771b260e4d9c285aebad82f799253f02210085b33d9186b18e92bbb5cb344b1fe586afee9a15e6ff8f3403dbf74815ff6a48:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,44 @@
+id: password-policy-expiration-unconfigured
+
+info:
+  name: RAM Password Policy Expiration - Unconfigured
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba Cloud RAM Password Policy is unconfigured, leaving user accounts vulnerable to weak or expired passwords. This lack of a configured policy may lead to potential unauthorized access due to weak password management.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/require-password-expiration-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers-condition: and
+    matchers:
+      - type: regex
+        regex:
+          - '"MaxPasswordAge":\s*(9[1-9]|[1-9][0-9]{2,})'  # Matches values greater than 90
+
+      - type: regex
+        regex:
+          - '"MaxPasswordAge":\s*(0|[1-9][0-9]?)'  # Excludes values between 0 and 90
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Expiration is Greater than 90 Days "'
+# digest: 490a0046304402207549bde74799cf714c472d8f8730a35eaa38a938692866df1904d0bd21ef7687022034a74ab5e9e73f0cf753ba6c4aaa75c4ec50913741389f2f63b7dcfdd63a2fc3:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,46 @@
+id: password-policy-length-unconfigured
+
+info:
+  name: RAM Password Policy requires Minimum Length 14 or Greater
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba RAM password policy is not configured to require a minimum length of 14 characters. This misconfiguration allows users to set shorter, potentially weaker passwords, increasing the risk of brute-force attacks.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/require-14-characters-password-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+
+    matchers-condition: and
+    matchers:
+      - type: regex
+        regex:
+          - \"MinimumPasswordLength\":\s*(1[4-9]|[2-9][0-9]{1,})
+        negative: true
+
+      - type: regex
+        regex:
+          - \"MinimumPasswordLength":\s*(\d|1[0-3])
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Does not contain Minimum Length "'
+# digest: 490a0046304402205d4196e02a5a3b0a4f7a8387344582cb697cd529c94f8b327a7b9c08de4945b002201f64123e410f44a14463f33f9b2bdd28b5c386eaa43fc7db3bf60ba2cf678ecf:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,39 @@
+id: password-policy-lowercase-unconfigured
+
+info:
+  name: RAM Password Policy requires atleast One Lowercase - Unconfigured
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba RAM password policy is not configured to require at least one lowercase letter in passwords. This misconfiguration may result in weak passwords, increasing the risk of unauthorized access.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/lowercase-letter-password-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"RequireLowercaseCharacters": false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Does not contain One Lowercase "'
+# digest: 4a0a00473045022058492c7376d065fd9a4bd5b0f6c3de42c2a7b15b7a4dff29f157fc0e69ec3e2f022100e845dd85858662f51084f880b16dc238a6c7f498a69cb478e8815f3cd9ede17d:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,39 @@
+id: password-policy-num-unconfigured
+
+info:
+  name: RAM Password Policy requires atleast One Number - Unconfigured
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba RAM password policy does not enforce the inclusion of at least one numeric character, increasing the risk of weak passwords and potential unauthorized access.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/require-number-password-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"RequireNumbers": false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Does not contain One Number "'
+# digest: 490a00463044022020adf9739a13e0165e1c00e9ee425937191afd8c32a862f78383aa8901adc959022036afc09b6c217d87bdda0309426e4c5780459da865ee72c378f8e7a8872dd641:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,39 @@
+id: password-policy-reuse-enabled
+
+info:
+  name: RAM Password Policy Reuse - Enabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba Cloud RAM (Resource Access Management) password policy reuse is disabled, meaning users are not restricted from reusing old passwords. This lack of a configured password history policy increases the risk of users reusing weak, previously compromised, or easily guessable passwords, which could lead to unauthorized access.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/prevent-password-reuse-password-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"PasswordReusePrevention": 0'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Allows Users Re-Use Old Password "'
+# digest: 4a0a00473045022038d771b00b065b69552986f0255e955ada91cf894490f78ccd8dfd884cd45d54022100b2615506c64bcd841fef1b4d99c7c65d10acfce3feb2022405ab01f749c5834a:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,39 @@
+id: password-policy-symbol-unconfigured
+
+info:
+  name: RAM Password Policy requires atleast One Symbol - Unconfigured
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba Cloud RAM password policy is unconfigured to require at least one symbol, leaving user accounts vulnerable to weak passwords. Enforcing this requirement is essential to ensure stronger, more secure passwords and reduce the risk of unauthorized access.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/require-symbol-password-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"RequireSymbols": false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Does not contain One Symbol "'
+# digest: 4b0a00483046022100fbcf64ed10963ef6c5ab722e556f906d1dc1de40dbe530d92050f8204af6e9b6022100d2c96ba77e32dbe2bb0467363d98de73b94dc328b9adae761a51a3b507e59334:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,39 @@
+id: password-policy-uppercase-unconfigured
+
+info:
+  name: RAM Password Policy requires atleast One Uppercase - Unconfigured
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The Alibaba RAM password policy is not configured to require at least one uppercase letter in passwords. This misconfiguration may result in weak passwords, increasing the risk of unauthorized access.
+  reference:
+    - https://www.alibabacloud.com/help/en/ram/user-guide/configure-a-password-policy-for-ram-users
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RAM/uppercase-letter-password-policy.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-ram
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun ram GetPasswordPolicy --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"RequireUppercaseCharacters": false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"RAM Password Policy Does not contain One Uppercase "'
+# digest: 4a0a00473045022100c499cd44ffa83f03e9c8fb263c637807c5715cb8e91ee70177758ccf4bb30a1b0220761da466ac954977004228aebfb485f970d35c750c42647a60d86e8b7788bac6:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,60 @@
+id: encryption-intransit-disabled
+
+info:
+  name: RDS Encryption in Transit - Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    Encryption in transit for Alibaba Cloud RDS is disabled, exposing data transmission to potential interception and unauthorized access.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/configure-ssl-encryption-for-an-apsaradb-rds-for-mysql-instance
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-encryption-in-transit.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeDBInstanceSSL --DBInstanceId $dbinstanceid --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"SSLEnabled": "No"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " RDS Encryption in Transit is Disabled "'
+# digest: 4b0a004830460221008975c054537a43ffe8ff1465de493660483ef4e72f1f6a18862dfa18b710ca13022100d7e92bcb5bf853223af4bb77099236fe3789fbd45bb45b226ae878ac38c089ae:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: log-connections-disabled
+
+info:
+  name: PostgreSQL "log_connections" Parameter - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The log_connections parameter in PostgreSQL is disabled, meaning the database does not log new client connections. This may limit the ability to monitor and track when clients connect to the database for security and auditing purposes.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-postgresql/use-a-parameter-template-to-configure-the-parameters-of-apsaradb-rds-for-postgresql-instances
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-log-connections-for-postgresql.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeParameters --DBInstanceId $dbinstanceid --region $region | jq -r '.RunningParameters.DBInstanceParameter[] | select(.ParameterName == "log_connections") | {ParameterName, ParameterValue}'
+
+    matchers:
+      - type: word
+        words:
+          - '"ParameterValue": "off"'
+          - '"ParameterName": "log_connections"'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " RDS log_connections Parameter for PostgreSQL Database Instances "'
+# digest: 4a0a00473045022078a4e044bf6cf5e47d63412049b74edf9c64b7f42127e7475656e08cc5e206ef022100a1e5174f0f1daf3fc9e6a8a3c2b496601a3832b61f19bdf35f71aa0922bcd22f:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: log-disconnections-disabled
+
+info:
+  name: PostgreSQL "log_disconnections" Parameter - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The log_disconnections parameter in Alibaba Cloud RDS for PostgreSQL is disabled, meaning the database does not log session disconnections. This can hinder the ability to audit and analyze database connection activities effectively.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-postgresql/use-a-parameter-template-to-configure-the-parameters-of-apsaradb-rds-for-postgresql-instances
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-log-disconnections-for-postgresql.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeParameters --DBInstanceId $dbinstanceid --region $region | jq -r '.RunningParameters.DBInstanceParameter[] | select(.ParameterName == "log_disconnections") | {ParameterName, ParameterValue}'
+
+    matchers:
+      - type: word
+        words:
+          - '"ParameterValue": "off"'
+          - '"ParameterName": "log_disconnections"'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " RDS log_disconnections Parameter for PostgreSQL Database Instances "'
+# digest: 490a0046304402204e59b359a41fbd61fcff314b9f6c690ff24cd3dcfae57b0a9d6231bfb926f572022073e6ada8dae4a9d5c47cd0a64190ab068743738eed07939af2963d0dab4498f7:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: log-duration-disabled
+
+info:
+  name: PostgreSQL "log_duration" Parameter - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The log_duration parameter in PostgreSQL is disabled, meaning the database does not log the duration of SQL queries. This can make it difficult to monitor and analyze query performance or identify slow-running queries for optimization.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-postgresql/use-a-parameter-template-to-configure-the-parameters-of-apsaradb-rds-for-postgresql-instances
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-log-duration-for-postgresql.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeParameters --DBInstanceId $dbinstanceid --region $region | jq -r '.RunningParameters.DBInstanceParameter[] | select(.ParameterName == "log_duration") | {ParameterName, ParameterValue}'
+
+    matchers:
+      - type: word
+        words:
+          - '"ParameterValue": "off"'
+          - '"ParameterName": "log_duration"'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " RDS log_duration Parameter for PostgreSQL Database Instances "'
+# digest: 4a0a00473045022100b06ccbd5514c7efc8fe339304a4b8eca3059658f4fd88bec14f522d88b368bed022041a7e867fd144c3a2d560fb2699b1792f4b46cb494a94e3f4b5f4181daf5b812:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: mssql-audit-disabled
+
+info:
+  name: Microsoft SQLServer Database Instances - SQL Auditing Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    SQL auditing is disabled on the MySQL database instances, meaning activities such as user queries and connection events are not logged. This may hinder the ability to track database activity, detect suspicious behavior, and comply with security auditing requirements.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/use-the-sql-explorer-and-audit-feature-on-an-apsaradb-rds-for-mysql-instance
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-sql-server-audit-logs.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --Engine SQLServer --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeSQLCollectorPolicy --DBInstanceId $dbinstanceid --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"SQLCollectorStatus": "Disabled"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " Microsoft SQLServer Database Instances SQL Auditing Disabled "'
+# digest: 4b0a00483046022100b12f7027262fdb72ae5cb4dda1491d4326f5236a6583ffc7ed3852b8810adc10022100d5ee7c6f58d43a06e8d8ae7eb554c286a67b07532971aa659d4ed79a8dfd5467:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: mysql-audit-disabled
+
+info:
+  name: MySQL Database Instances - SQL Auditing Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    SQL auditing is disabled on the MySQL database instances, meaning activities such as user queries and connection events are not logged. This may hinder the ability to track database activity, detect suspicious behavior, and comply with security auditing requirements.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/use-the-sql-explorer-and-audit-feature-on-an-apsaradb-rds-for-mysql-instance
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-mysql-audit-logs.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --Engine MySQL --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeSQLCollectorPolicy --DBInstanceId $dbinstanceid --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"SQLCollectorStatus": "Disabled"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " MySQL Database Instances SQL Auditing Disabled "'
+# digest: 490a0046304402205a1185f2c0c30f07ffd9e058302d352539f591ef9f9b70d138ed10ff3214bf11022036b2bfdece214484a0fea82769f3b63f634ee1118a3681191aed816759316068:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: postgresql-audit-disabled
+
+info:
+  name: PostgreSQL Database Instances - SQL Auditing Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    SQL auditing is disabled on the PostgreSQL database instances, meaning activities such as user queries and connection events are not logged. This may hinder the ability to track database activity, detect suspicious behavior, and comply with security auditing requirements.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-postgres-audit-logs.html
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-postgresql/use-the-sql-explorer-and-audit-feature-on-an-apsaradb-rds-for-postgresql-instance
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("instance", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --Engine PostgreSQL --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeSQLCollectorPolicy --DBInstanceId $dbinstanceid --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"SQLCollectorStatus": "Disabled"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'instance + " PostgreSQL Database Instances SQL Auditing Disabled "'
+# digest: 4a0a00473045022100ce7c455a2ed9fdab36bc318389f3676c5b38da1642eb7c681c2298b3f2dcc024022057f0fb86ab309677a3c7e9f5ae172202b612be0712c5368c996c4428df8a4c70:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: rds-audit-disabled
+
+info:
+  name: RDS Database Instances - SQL Auditing Disabled
+  author: DhiyaneshDK
+  severity: high
+  description: |
+    SQL auditing is disabled on the RDS Database instances, meaning activities such as user queries and connection events are not logged. This may hinder the ability to track database activity, detect suspicious behavior, and comply with security auditing requirements.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/use-the-sql-explorer-and-audit-feature-on-an-apsaradb-rds-for-mysql-instance
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-audit-logs.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("dbinstanceid", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeSQLCollectorPolicy --DBInstanceId $dbinstanceid --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"SQLCollectorStatus": "Disabled"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'dbinstanceid + " RDS Database Instances SQL Auditing Disabled "'
+# digest: 490a00463044022028cdca0356b150bd29ac95327a5eb276331cde830eff7be2feec1c94f668f18902204652c90b1da9d39f6bc71d842c3e4ceaabbf28b4bf0c39a813baa1f523fa18cb:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: transparent-encryption-disabled
+
+info:
+  name: Transparent Data Encryption - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Alibaba Cloud Transparent Data Encryption (TDE) is disabled, meaning sensitive data at rest is not encrypted automatically. This may expose the data to unauthorized access, compromising confidentiality and security.
+  reference:
+    - https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-postgresql/enable-tde-for-an-apsaradb-rds-for-postgresql-instance-and-use-tde
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-RDS/enable-sql-database-tde.html
+  metadata:
+    max-request: 2
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-rds
+
+variables:
+  region: "cn-hangzhou"
+
+flow: |
+  code(1)
+  for(let DBInstanceId of iterate(template.dbinstanceid)){
+    set("dbinstanceid", DBInstanceId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun rds DescribeDBInstances --region $region
+
+    extractors:
+      - type: json
+        name: dbinstanceid
+        internal: true
+        json:
+          - '.Items.DBInstance[].DBInstanceId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun rds DescribeDBInstanceTDE --DBInstanceId $dbinstanceid --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"TDEStatus": "Disabled"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'dbinstanceid + " Transparent Data Encryption is Disabled "'
+# digest: 490a004630440220124e98dd4905cc95b3f61fe3ce77c32f5753feed8760539b76e8d8414dff15de02203f33711fafa6819d58182b4652d88435a1dabb7f4d7a93130ec81ef27116b5fc:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,39 @@
+id: scheduled-vulnscan-disabled
+
+info:
+  name: Scheduled Vulnerability Scan - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The automated vulnerability scanning feature is turned off, preventing regular checks for security weaknesses. This increases the risk of undetected vulnerabilities in the system.
+  reference:
+    - https://www.alibabacloud.com/help/en/security-center/user-guide/scan-for-vulnerabilities
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-SecurityCenter/enable-scheduled-vulnerability-scan.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,security-center
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun sas DescribeVulConfig --region $region
+
+    matchers:
+      - type: word
+        name: policy
+        words:
+          - '"Config": "off"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"Scheduled Vulnerability Scan is Disabled "'
+# digest: 490a0046304402206c02830649fd1a4625f43a0339e4d3b03efda89840d274c8b94a54928878845d02207b010d79b6248d8df3e457e7550bafc969967a0f87d0b491911c9db87c527e5b:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,46 @@
+id: security-notification-disabled
+
+info:
+  name: Security Center Notifications - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Notifications for Alibaba Security Center are disabled, which may result in missed alerts for critical security events.
+  reference:
+    - https://www.alibabacloud.com/help/en/security-center/user-guide/use-the-notification-feature
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-SecurityCenter/enable-high-risk-item-notifications.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,security-center
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun sas DescribeNoticeConfig --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"Route": 0'
+          - '"Project":'
+        condition: and
+
+    extractors:
+      - type: json
+        name: noticeconfiglist
+        internal: true
+        json:
+          - '.NoticeConfigList | map(select(.Route == 0) | .Project)'
+
+      - type: dsl
+        dsl:
+          - '"Project: " + noticeconfiglist + " Security Center Notifications are Disabled"'
+# digest: 4b0a00483046022100827955f622c0bbf7651c3c6b3431aff9f25ede363c0cac2721eda13d5726a5a4022100d2a8d1e0a7c64807f03223acd88f50250a91ee5437866f68ed7a6731a291712c:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,40 @@
+id: security-plan-disabled
+
+info:
+  name: Security Center Plan - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure your Alibaba Cloud Security Center is on the Advanced or Enterprise Edition for enhanced security features like malware detection, webshell identification, and anomaly recognition. Upgrading provides critical protection against undetected threats.
+  reference:
+    - https://www.alibabacloud.com/help/en/security-center/product-overview/upgrade-and-downgrade-security-center
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-SecurityCenter/security-center-plan.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,security-center
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun sas DescribeVersionConfig --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"IsPaidUser": false'
+          - '"Version": 1'
+        condition: and
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '" Security Center Plan is Not Configured to Enterprise or Advance Edition "'
+# digest: 4a0a00473045022100ddf5ad89ed8b0bec452536604f4644db143949178d1a3c98a9e50a1b3b0c0d1c02207ad46afe86a5e613808f1d73c1bb5411e803b114cb49423d6f14d1034de91d25:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: vpc-flow-disabled
+
+info:
+  name: VPC Flow Log - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    The VPC Flow Log is disabled, meaning network traffic data is not being captured or monitored. This lack of logging reduces visibility into network activities, making it difficult to detect and investigate potential security incidents or performance issues.
+  reference:
+    - https://www.alibabacloud.com/help/en/vpc/user-guide/create-and-manage-flow-log
+    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/alibaba-cloud/AlibabaCloud-VPC/enable-flow-logs.html
+  metadata:
+    max-request: 1
+    verified: true
+  tags: cloud,devops,aliyun,alibaba,alibaba-cloud-config,alibaba-vpc
+
+variables:
+  region: "cn-hangzhou"
+
+self-contained: true
+
+flow: |
+  code(1)
+  for(let VpcId of iterate(template.vpcid)){
+    set("vpc", VpcId)
+    code(2)
+  }
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aliyun vpc DescribeVpcs --region $region
+
+    extractors:
+      - type: json
+        name: vpcid
+        internal: true
+        json:
+          - '.Vpcs.Vpc[].VpcId'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aliyun vpc DescribeFlowLogs --RegionId $region --VpcId $vpcid
+
+    matchers:
+      - type: word
+        words:
+          - '"FlowLog": []'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'vpcid + " VPC Flow Log is Disabled "'
+# digest: 490a004630440220721651a199ad66d9248c520014a542df1de8ee0e95aa8b20688be059ffc1b07902204763733958bc565151af0a403d7ca951193862779fdaa488e62726dca8ed2151:922c64590222798bb761d5b6d8e72950
@@ -38,4 +38,4 @@ code:
      - type: dsl
        dsl:
          - 'region + " AWS region have expired SSL/TLS certificates"'
-# digest: 490a00463044022020875df0814bb41d33d015a50a6a2d23309be5b695bad8ba9840f77e139f719b02205052abd88786969a3d7dcc2594b881841f82308df082a71df3b221085d1e9ceb:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502207c3e71e79a28c959cf8f3595a0f9e9ec0d767a45145e7ad17689021ba4f696ed022100a2e40286c09afd8ef29dac3b6de54a7ecc1fd0475655955f7a25fc6b1c9864d9:922c64590222798bb761d5b6d8e72950
@@ -55,4 +55,4 @@ code:
      - type: dsl
        dsl:
          - '"The AWS ACM Certificate " + certificate +" is about to expire in 30 days"'
-# digest: 4b0a00483046022100bc7d6e62968fc709c8201354d29b61784664ef5c5ebed70a6a8b305447b93725022100bad54d48aab6fdd1356608d1940730ea10536641398de6172861695612abd412:922c64590222798bb761d5b6d8e72950
+# digest: 490a004630440220243fb2914333499fae730b472688256b5a3efec50ba804e061787fe3e4ca514402204e288a97312494ca3b200361da1cac4bf86c99217569211c89a30c226389e960:922c64590222798bb761d5b6d8e72950
@@ -55,4 +55,4 @@ code:
      - type: dsl
        dsl:
          - '"The AWS ACM Certificate " + certificate +" is about to expire in 30 days"'
-# digest: 490a0046304402202b2fedb03a19db3f9d0f87fdc3982c926a2478e6e2903d2fbb55b63561d3a29c0220337c43e0512cc540287235d9f3489fb5af0dc783ae118c4341c27e2812a8d8c7:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100afa1e5b4ba6aeef0412564db36b6a727b3b10a17c6e90c745eaa7bf211398e18022100c5777c658dfc8695d06f6583b161f77b996454b09af2203bb799d85034fe6e12:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"The issue/renewal request for " + certificatearn + " SSL/TLS certificate was not validated"'
-# digest: 4a0a0047304502210092b18eb3a24d6dea12fc385763c84745bf8201424ef620661e9c9fbb1b3b513a02201dc10c6f007cea631d51e81c2b6c883bf6c530a4de13398dea1c605b4a925714:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a004830460221009c4c06dcc6415ac0bc7fc6357f399c97951c8c2af78cfd03f46c903b41586eb6022100e250115449f872d9360678566e7f3457e86e96cb1ad4f24007deb8309f810b3d:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - 'certificatearn + " AWS ACM certificate is a wildcard certificate"'
-# digest: 4a0a00473045022078c25c2aeb4e1ecb7851bfcf3e176bbd0eff547432a2a5ec04d150b1c3fbfdaf022100b3e428a513082fb7357f95e92309d0dfe47823bc6eb40cc403cc2836756ccd60:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100dbca7d2794c441a99df146a95cbce9fbdab400e333759e871cc37e8a268dd285022100f1d219c3674cb0992bbbbdd52439f972c0673e313ac4923ef82b226077cbc405:922c64590222798bb761d5b6d8e72950
@@ -52,4 +52,4 @@ code:
      - type: dsl
        dsl:
          - '"AWS CLI is properly configured for account \"" + account + "\" and all the necessary tools required are installed"'
-# digest: 4b0a00483046022100c79a6583acb05a00dfa742962972031f8c42ae9ce85aabc1c9edb1ae7ebd9368022100b98762cb406a952a4115e28bb639f0d16d02e0b737012da638e3bf3f5d73f5f5:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022052484996550fb7281548c8303d5073f5afe21282edd02f6b44327849754db470022100e00b95fbe7c0069c51b67f29380e776144f64464de6aa670a8bcf248722b0e69:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: stack-notification-disabled
+
+info:
+  name: CloudFormation Stack Notification - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that your Amazon CloudFormation stacks are using SNS topics to send notifications when important events occur.
+  impact: |
+    Disabling CloudFormation Stack Notifications can lead to reduced visibility into stack events and errors, delaying the detection of issues and hindering effective monitoring of changes and deployments in the cloud environment.
+  remediation: |
+    Enable CloudFormation Stack Notifications by configuring SNS (Simple Notification Service) topics for your CloudFormation stack. This will ensure real-time alerts on stack events, including updates, errors, and resource creation, providing better monitoring and visibility.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFormation/cloudformation-stack-notification.html
+    - http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-stack.html
+  tags: cloud,devops,aws,amazon,cloudformation,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let StackSummaries of iterate(template.stacksummaries)){
+    set("stacksummary", StackSummaries)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aws cloudformation list-stacks --region $region --stack-status-filter CREATE_COMPLETE --output json --query 'StackSummaries[*].StackName'
+
+    extractors:
+      - type: json
+        name: stacksummaries
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+        aws cloudformation describe-stacks --region $region --stack-name $stacksummary --query 'Stacks[*].NotificationARNs[]'
+
+    matchers:
+      - type: word
+        words:
+          - '[]'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFormation Stack Notification " + stacksummary + " is Disabled"'
+# digest: 4a0a00473045022100bc25a76faa0c7e58a4a92eb2f19a3274305669771d48c016d498e89c11662c5e02203a98e65faea988f9df8e4a27ba1c90ebfe9fb35920fbdaaaa0d8e8231552a475:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: stack-policy-not-inuse
+
+info:
+  name: CloudFormation Stack Policy - Not In Use
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure your AWS CloudFormation stacks are using policies as a fail-safe mechanism in order to prevent accidental updates to stack resources.
+  impact: |
+    Lack of a CloudFormation Stack Policy allows unrestricted modifications to stack resources, increasing the risk of unintended or harmful changes.
+  remediation: |
+    Implement a CloudFormation Stack Policy to restrict updates to critical resources, defining explicit rules for which resources can be modified during stack updates.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFormation/cloudformation-stack-policy.html
+    - http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/protect-stack-resources.html
+  tags: cloud,devops,aws,amazon,cloudformation,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let StackSummaries of iterate(template.stacksummaries)){
+    set("stacksummary", StackSummaries)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aws cloudformation list-stacks --region $region --output json --query 'StackSummaries[*].StackName'
+
+    extractors:
+      - type: json
+        name: stacksummaries
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+        aws cloudformation get-stack-policy --region $region --stack-name $stacksummary --output json
+
+    matchers:
+      - type: word
+        words:
+          - 'StackPolicyBody'
+          - 'Effect'
+        negative: true
+
+    extractors:
+      - type: dsl
+        dsl:
+          - 'stacksummary + " No Stack Policy In Use"'
+# digest: 4b0a00483046022100a746affd01686c4b233d818424db502ef0dd44c73af71e06408ad6643c49817b022100ec9758a323f48a9ec00e94eb8669ad58551fd8b2cbb8fc0d1ad835020645cd13:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,59 @@
+id: stack-termination-disabled
+
+info:
+  name: CloudFormation Termination Protection - Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that Termination Protection safety feature is enabled for your Amazon CloudFormation stacks in order to protect them from being accidentally deleted.
+  impact: |
+    Disabled termination protection increases the risk of accidental deletion of critical CloudFormation stacks.
+  remediation: |
+    Enable termination protection for critical CloudFormation stacks by setting TerminationProtection to true in the stack settings, preventing accidental deletions.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFormation/stack-termination-protection.html
+    - http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-protect-stacks.html
+  tags: cloud,devops,aws,amazon,cloudformation,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let StackSummaries of iterate(template.stacksummaries)){
+    set("stacksummary", StackSummaries)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      aws cloudformation list-stacks --region $region --stack-status-filter CREATE_COMPLETE --output json --query 'StackSummaries[*].StackName'
+
+    extractors:
+      - type: json
+        name: stacksummaries
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+    source: |
+        aws cloudformation describe-stacks --region $region --stack-name $stacksummary --query 'Stacks[*].EnableTerminationProtection' --output json
+
+    matchers:
+      - type: word
+        words:
+          - 'false'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFormation Termination Protection " + stacksummary + " is Disabled"'
+# digest: 4b0a004830460221008a2e3415182e202a607c9e30aa6cbac326038dd23f1209a7c133a713cc21b2730221009f32c2fb6c20a62e81094b8fbe1ad127c36237c9c6c813edf579d3c7ddc2983c:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-compress-object
+
+info:
+  name: CloudFront Compress Objects Automatically
+  author: DhiyaneshDK
+  severity: low
+  description: |
+    Ensure that your Amazon CloudFront Content Delivery Network (CDN) distributions are configured to automatically compress content for web requests that include "Accept-Encoding: gzip" in the request header, in order to increase the websites/web applications performance and reduce bandwidth costs.
+  impact: |
+    Disabling "Compress Objects Automatically" in CloudFront can lead to increased data transfer costs and slower page load times, negatively impacting user experience and performance.
+  remediation: |
+    Enable "Compress Objects Automatically" in CloudFront to reduce data transfer sizes, enhance loading speeds, and improve overall performance for end users.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/compress-objects-automatically.html
+    - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/ServingCompressedFiles.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution-config --id $distribution --query 'DistributionConfig.CacheBehaviors.Items[*].Compress' --region $region --output text
+
+    matchers:
+      - type: word
+        words:
+          - "False"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Compress Objects Automatically " + distribution + " is Disabled"'
+# digest: 4a0a0047304502210094de0b064b70663a82dba4b63ac8d5b2663b8251696fd3bba81d0a375c0fcbe7022018997148c58889699314b47fb7586b8ca1d4092bc320438bfab6d104904fe6ac:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-custom-certificates
+
+info:
+  name: Cloudfront Custom SSL/TLS Certificates - In Use
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that your Amazon CloudFront distributions are configured to use a custom SSL/TLS certificate instead of the default one.
+  impact: |
+    Failing to use custom SSL/TLS certificates in CloudFront can result in trust issues with end users, exposing your web content to man-in-the-middle attacks and potentially damaging your brand's reputation due to untrusted connection warnings.
+  remediation: |
+    Configure your Amazon CloudFront distribution to use custom SSL/TLS certificates to ensure secure and trusted connections for your users, enhancing data protection and maintaining brand integrity.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/cloudfront-distro-custom-tls.html
+    - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution --region $region --id $distribution --query 'Distribution.DistributionConfig.ViewerCertificate.CloudFrontDefaultCertificate' --output text
+
+    matchers:
+      - type: word
+        words:
+          - "False"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"Cloudfront Custom SSL/TLS Certificates " + distribution + " In Use"'
+# digest: 4b0a00483046022100f4348f4cb85e838f5be2e607133e43a5b3a4c72fdc94fd193eded1206bd6e1eb022100f883292e3ccc805f74f4d647813d0575945275eb447ae0f08901b9c3700fb162:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-geo-restriction
+
+info:
+  name: CloudFront Geo Restriction - Not Enabled
+  author: DhiyaneshDK
+  severity: info
+  description: |
+    Ensure that geographic restriction is enabled for your Amazon CloudFront CDN distributions in order to allow or block viewers from specific locations (countries) from accessing your web content.
+  impact: |
+    Not enabling Geo Restriction in CloudFront exposes content to users from unauthorized regions, increasing the risk of content misuse, compliance violations, and potential security threats.
+  remediation: |
+    Enable Geo Restriction in CloudFront to control access to content based on geographic locations, ensuring only authorized users from designated regions can access specific resources.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/geo-restriction.html
+    - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/georestrictions.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution-config --id $distribution --query "DistributionConfig.Restrictions.GeoRestriction.RestrictionType" --region $region --output text
+
+    matchers:
+      - type: word
+        words:
+          - "none"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Compress Objects Automatically " + distribution + " is Disabled"'
+# digest: 4b0a00483046022100ae8efc4f803814a5fc310174a16c555a56e74965bbe71f368be319f2099aaf75022100f86d42da45940d19950c1cc38c99ea9bbc51db0be308ac041d61c03c32c58782:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-insecure-protocol
+
+info:
+  name: CloudFront Insecure Origin SSL Protocols
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that your Amazon CloudFront Content Delivery Network (CDN) distributions are not using insecure SSL protocols (i.e. SSLv3) for HTTPS communication between CloudFront edge locations and custom origins.
+  impact: |
+    Insecure SSL protocols for CloudFront origins can expose sensitive data to interception and compromise, increasing the risk of man-in-the-middle attacks.
+  remediation: |
+    Configure your CloudFront distribution to enforce the use of secure SSL/TLS protocols (TLS 1.2 or higher) for all origins and disable support for outdated protocols like SSLv3 and TLS 1.0/1.1.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/cloudfront-insecure-origin-ssl-protocols.html
+    - http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/SecureConnections.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution --id $distribution --query 'Distribution.DistributionConfig.Origins.Items[*].CustomOriginConfig.OriginSslProtocols.Items | []' --region $region --output json
+
+    matchers:
+      - type: word
+        words:
+          - "SSLv3"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Uses SSLv3 Protocol in" + distribution'
+# digest: 490a0046304402203f82a403b2d5299d4e40fe21ec8d29df8dca63b594e26c055fb1aea9e3b183e9022070d55cd893d231f70803f0755dfbf169c2917ea01d600a785c3b5e5e4277a9ae:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,67 @@
+id: cloudfront-integrated-waf
+
+info:
+  name: CloudFront Integrated With WAF
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that all your Amazon CloudFront distributions are integrated with the Amazon Web Application Firewall (WAF) service to protect against application-layer attacks that can compromise the security of your websites/web applications or place unnecessary load on them
+  impact: |
+    Lack of integration between CloudFront and a Web Application Firewall (WAF) increases vulnerability to web-based attacks, including DDoS, SQL injection, and cross-site scripting (XSS).
+  remediation: |
+    Integrate CloudFront with an appropriate Web Application Firewall (WAF) to filter and monitor HTTP requests, providing enhanced protection against common web threats.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/cloudfront-integrated-with-waf.html
+    - http://docs.aws.amazon.com/waf/latest/developerguide/what-is-aws-waf.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution --id $distribution --query 'Distribution.DistributionConfig.WebACLId' --region $region --output json
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        words:
+          - '""'
+
+      - type: word
+        words:
+          - 'arn:'
+        negative: true
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Integrated With WAF " + distribution + " is Disabled"'
+# digest: 4a0a0047304502202d620642cc74990fe24716a6835537c17f0665b4f33110c47f495fa92f709ea1022100d5da002654b1eb9447b384320856fdac406517a81f3fea768bb8c0caacddd897:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-logging-disabled
+
+info:
+  name: Cloudfront Logging Disabled
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that access (standard) logging is enabled for your Amazon CloudFront distributions in order to track all viewer requests for the web content delivered through the Content Delivery Network (CDN).
+  impact: |
+    Disabling CloudFront logging reduces visibility into traffic patterns, hinders incident response and forensic analysis, compromises compliance efforts, and limits troubleshooting capabilities, increasing security risks.
+  remediation: |
+    Enable encryption for all existing EBS volumes and ensure that all new volumes created are configured to use encryption by default. Additionally, update any snapshots to be encrypted and use AWS Key Management Service (KMS) to manage encryption keys securely.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/cloudfront-logging-enabled.html
+    - http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution --id $distribution --query 'Distribution.DistributionConfig.Logging.Enabled' --region $region --output text
+
+    matchers:
+      - type: word
+        words:
+          - "False"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"Cloudfront Logging " + distribution + " is Disabled"'
+# digest: 4a0a0047304502200285c729ba0b638126b679fa50d620ddaa0c8ccf98e7fb0d5292f8f7f544746c022100e46eb51abb3cb736a33c0648ff14957f1285349c4e4f5bc69dc2ad222e1dc07b:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-origin-shield
+
+info:
+  name: CloudFront Origin Shield - Not Enabled
+  author: DhiyaneshDK
+  severity: info
+  description: |
+    Ensure that the Origin Shield performance optimization feature is enabled for all your Amazon CloudFront distributions in order to help reduce the load on your distribution's origin, improve its availability, and reduce its operating costs.
+  impact: |
+    Not enabling CloudFront Origin Shield can lead to increased load on your origin server, higher latency, and greater costs due to more frequent requests during traffic spikes.
+  remediation: |
+    Enable CloudFront Origin Shield for your distributions to optimize cache efficiency, reduce load on your origin server, and improve content delivery performance during high traffic periods.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/enable-origin-shield.html
+    - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/origin-shield.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution-config --id $distribution --query 'DistributionConfig.Origins.Items[*].OriginShield.Enabled' --region $region --output text
+
+    matchers:
+      - type: word
+        words:
+          - "False"
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Origin Shield " + distribution + " not Enabled"'
+# digest: 4b0a00483046022100dd96e4176b628f6bde5087c60dd3c52d1025a52dc88c1c70250636f051baab9702210096d6a9b2cf84d6c1bcf08bbb6f2a8bf521313a4213d1c7f30bc7af41949c4c03:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,65 @@
+id: cloudfront-security-policy
+
+info:
+  name: CloudFront Security Policy
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that your Amazon CloudFront distributions are using a security policy with minimum TLSv1.2 or TLSv1.3 and appropriate security ciphers for HTTPS viewer connections.
+  impact: |
+    Failing to use a security policy with a minimum of TLSv1.2 or TLSv1.3 and appropriate ciphers for HTTPS viewer connections in CloudFront can expose sensitive data to interception and reduce the overall security of your application.
+  remediation: |
+    Configure your Amazon CloudFront distributions to use a security policy that enforces a minimum of TLSv1.2 or TLSv1.3 and specifies secure ciphers for HTTPS viewer connections.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/security-policy.html
+    - https://aws.amazon.com/about-aws/whats-new/2017/09/amazon-cloudfront-now-lets-you-select-a-security-policy-with-minimum-tls-v1_1-1_2-and-security-ciphers-for-viewer-connections/
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution --id $distribution --query 'Distribution.DistributionConfig.ViewerCertificate.MinimumProtocolVersion' --region $region --output json
+
+    matchers:
+      - type: word
+        words:
+          - '"TLSv1"'
+          - '"TLSv1_2016"'
+          - '"TLSv1.1_2016"'
+          - '"TLSv1.2_2018"'
+          - '"TLSv1.2_2019"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Uses Insecure Protocols " + distribution'
+# digest: 4b0a004830460221008c2f205519658e0b52736eb47e67a7a80b97db0fbf144406765b715caa5671070221008aa467383b6f43ebd7f7d4fa6c6f609ba95fafa2790aace7099570b6c5bcd980:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-traffic-unencrypted
+
+info:
+  name: CloudFront Traffic To Origin Unencrypted
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that the communication between your Amazon CloudFront distributions and their custom origins is encrypted using HTTPS in order to secure the delivery of your web content and fulfill compliance requirements for encryption in transit.
+  impact: |
+    Unencrypted traffic between CloudFront and custom origins can expose sensitive data during transmission, leading to potential data breaches and non-compliance with encryption standards.
+  remediation: |
+    Ensure that all communications between your Amazon CloudFront distributions and custom origins are encrypted by configuring them to use HTTPS, thereby securing the delivery of web content and meeting compliance requirements for encryption in transit.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/cloudfront-traffic-to-origin-unencrypted.html
+    - http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/SecureConnections.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution --id $distribution --query 'Distribution.DistributionConfig.Origins.Items[*].CustomOriginConfig.OriginProtocolPolicy' --region $region --output json
+
+    matchers:
+      - type: word
+        words:
+          - '"http-only"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront " + distribution + " uses HTTP Only"'
+# digest: 4a0a00473045022100bfff3b1784cc0acf0fef51f467228b62784fcb9d9b3cd974296304ecbc5c95c70220728e3fd804a5f14282e58482febe903e75391471a5f25b9534ca99676f8965fc:922c64590222798bb761d5b6d8e72950
@@ -0,0 +1,61 @@
+id: cloudfront-viewer-policy
+
+info:
+  name: CloudFront Viewer Protocol Policy
+  author: DhiyaneshDK
+  severity: medium
+  description: |
+    Ensure that the communication between your Amazon CloudFront distribution and its viewers is encrypted using HTTPS in order to secure the delivery of your web content.
+  impact: |
+    Failing to enforce HTTPS for viewer connections in CloudFront can expose web content to interception and manipulation, compromising the security and integrity of sensitive data transmitted between users and the distribution
+  remediation: |
+    Configure your Amazon CloudFront distribution's viewer protocol policy to either redirect HTTP requests to HTTPS or require HTTPS connections exclusively, ensuring secure delivery of web content and protecting against potential data breaches.
+  reference:
+    - https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/CloudFront/viewer-protocol-policy.html
+    - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html
+  tags: cloud,devops,aws,amazon,cloudfront,aws-cloud-config
+
+variables:
+  region: "us-west-2"
+
+flow: |
+  code(1)
+  for(let DistributionListItemsId of iterate(template.distributions)){
+    set("distribution", DistributionListItemsId)
+    code(2)
+  }
+
+self-contained: true
+
+code:
+  - engine:
+      - sh
+      - bash
+
+    source: |
+      aws cloudfront list-distributions --output table --query 'DistributionList.Items[*].Id' --region $region --output json
+
+    extractors:
+      - type: json
+        name: distributions
+        internal: true
+        json:
+          - '.[]'
+
+  - engine:
+      - sh
+      - bash
+
+    source: |
+        aws cloudfront get-distribution-config --id $distribution --query 'DistributionConfig.CacheBehaviors.Items[*].ViewerProtocolPolicy' --output json --region $region
+
+    matchers:
+      - type: word
+        words:
+          - '"allow-all"'
+
+    extractors:
+      - type: dsl
+        dsl:
+          - '"CloudFront Viewer Policy " + distribution + " allows all"'
+# digest: 490a004630440220768d2a4c15a0516365ef4fe8d25f47e5c0f96c483617c859a77548cfe800ff5202204ab9615b2800dec6a7b7118656bad06d1f33ec1a43040081e0fc53d622215b36:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail" + trail + " is not configured to capture resource operations performed on or within an AWS cloud resource"'
-# digest: 4b0a00483046022100da87f9b597db66bbcf87384782b53d2b838ad5c8b6c89924afc2607aa6c92bdf022100849208d4cb009645e9a5d9bf73dd7dfa351b390b23991bffa72a85d99ca0ac4c:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100d8d3d3939bb96ea7f7ede4cfb901cb01a7d9b4b1013bb775455332dc60c4d0e9022100d15ded970f22179552bc315212e51e4e8afb058dd5cfed5a4e7f020c4a16bba4:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail" + trail + " is not configured to receive log files from all the AWS cloud regions"'
-# digest: 4a0a00473045022100a7330af1aa9ad989dc95304b0e71f8479849de9782179443c3b7caf9d9373add022034c783da46b9b3b530bbb04d08b70e1803c5d298104e3d65659addd1a8c839d9:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100fca761ce5c95eeb781ebd2afec0ffa1659a8ea317ac44814ba9f866e086e0836022100c1eb1a17e68513ab1dea8246ee974a9ccfbfa55b77be8f0f9d2434a5f927c6cb:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"Ensure only one trail in Amazon CloudTrail is configured for global service events to avoid duplicates: " + trail'
-# digest: 4b0a00483046022100c35edad75ea1ac20bfb4e2cbe8b2b4e8fc3b29c40e7ff611808957ab6d83f303022100a77f7c148769b6ca2d6277298d4a5269e1bb2092f609f67cef8e8152a67f02eb:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100d1139235f7eab3bb93560b30c88ceda4eb8fa8c658cc821693198e7640bea17902210086106d9e04a589f3e46bbfa41593f4a8979c3af2fe342e2842e20a6ee03a35aa:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail" + trail + " is not configured to record API calls for AWS global services"'
-# digest: 4b0a00483046022100f10c2c9b4cb87ac0e4d1bdcdbf1f22db6d84b775136499410fe1fd92ba1ad9c5022100eecaa6515470a95ff633ad2df025ded9d8c20f051189a648b1f862861ceb3599:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100ad4752dd1f37d257de88d0a6b6355db49690bba904f5fbd3d45a1b7b38e1760e022100ec11a819b53b9e07542d121928b8ff464328ee9cb8eebca012f4cacfd3cb024f:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail" + trail + " is not configured to send events to CloudWatch Logs for monitoring purposes"'
-# digest: 4a0a004730450221008bdf150f8abb8be1e258c067aae73857443f219a130cf41d0cc3d9c0c6d45ab302205479a358041954f9d0aa04b2145860008c3732d303a381268f0c31a0148495dd:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022079c294096ed170716849b5fb7d05822bd381caa9fcfef87b21ce761be412ea43022100b59348b2f6da4316675f81e0640c8c0c5530730d6dca6d63ea603a0cad3323c3:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"The log file integrity validation is not enabled for CloudTrail trail" + trail'
-# digest: 4a0a00473045022100e301d2ce8df52b0170dbbbee6ca44cc69ea46fd81c0ff3dd3264dc81a8548c2402206321af47afdb4655e6ed862dbdc015d73cf98840e24c43636f0a2a28e2feb81c:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100db42b4c20d12be50805623fbaab88e9c15567c638ebd384bb98458c0c5d3034d02201378e79dbdd61fabf0a1416326e5047af6e1ac64e10aecd8d091285824f89f32:922c64590222798bb761d5b6d8e72950
@@ -61,4 +61,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail " + trail + " is not configured to encrypt log files using SSE-KMS encryption"'
-# digest: 4a0a00473045022100fb8aa2e414f88294926325f90076733d4a7d4af4ac18c47b9b82564412f5a2250220104bc5c6dcda1248db44229720dda05561319e3549bb6437ea1c97c6c099421c:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502205431dba97a21f5853b99739cb31114a978e5cce863034217b4dd523e67d4cb9d022100b809d1b226bffa89d8a592b2f08cd1063512e36b200cb911f11899a60a81d56d:922c64590222798bb761d5b6d8e72950
@@ -71,4 +71,4 @@ code:
      - type: dsl
        dsl:
          - '"The MFA Delete feature is not enabled for the S3 bucket " + bucket + " associated with the CloudTrail " + trail'
-# digest: 4a0a00473045022003bb18e55eae6aa19233a988216a85ab85d1321a68dee66dc295ce19735d9900022100bbfbf82a13f2a4e5693299287c29e50507941e1576d01425abdb7a5b0e68f775:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022074bcc46953d45bd74975aabebd753202688f9d3774e1d44137f0eede82c5d7ea022100b701b86493ae07d3699f7a259c8e77374645f752be2923b83f33fbed7848ecee:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail" + trail + " is not configured to capture management operations performed on your AWS cloud resources"'
-# digest: 4a0a00473045022100f0879bcbe45c9ed0c8921338f6384c009e9a4e2b4e9b8199e3b462fcb93ca7bb02202ba77a0927be3707abc226f4b5d0c4116cd8f2b4d463e8f822e8defbe7934e4e:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100c23af41ffe65ebbf7f4ea184345be1af712eb20af947b75194e060e21952e352022100b20648518cb36f80a826bfe23d60bda79468590ec8a3a9a34a412a45213a72ea:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"CloudTrail trail" + trail + " is not configured to record API calls for AWS global services"'
-# digest: 4a0a004730450220153c8058c6e3274fd6caf2b309baa876492c64fa5978590b21938000e9416aa6022100faaf8886e0deb971d17b2f325fc402814e59ce66ff16ea343543e3b6b3f13773:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a004730450221009199fc98dbbde4ee65e05efcf675a415ed8ec5b2e67e9804cb4a039f9cb6a59a02201ae662ec7da6b032d1dd62ba6ea0022da7bcec42c846387e7a62e53cc2cee466:922c64590222798bb761d5b6d8e72950
@@ -71,4 +71,4 @@ code:
      - type: dsl
        dsl:
          - '"Access logging is not enabled for the S3 bucket associated with CloudTrail trail " + trail'
-# digest: 4a0a00473045022100bfe94b20d18063458c694381cd23f96dd8023473e8b9e8151922295b88bff033022044b9f7a79baa2caa0d4ae5406a2701c73c77ddc43da72190b32f1e6ec1fa21ca:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100b36f560e682fdf7547761f0196415f58dabdfb3c892e1e2ac862566266708ed4022008f2f86f1b84d5f2efb9ae26f448a535ff7e8c19e6647875caf873448987101d:922c64590222798bb761d5b6d8e72950
@@ -72,4 +72,4 @@ code:
      - type: dsl
        dsl:
          - '"The Object Lock feature is not enabled for the S3 bucket associated with the CloudTrail trail " + trail'
-# digest: 4a0a00473045022100adf9327a943f74cada1c893502adad96b8db198c24c0211486944503bc818dc202205d41291ad41820b5afe0d7d1eb4061acde307124ff04b588b1cb3fbeec75f54c:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502206a9bee19bdcefd4c05c149a0aa0da4c07b77a768fb208897687b8e3c92425e510221008e6b2c80c6e79734c084560ad8640df0b977475c6561d4958bf7219e1a6d3fc7:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"The Amazon CloudWatch " + alarm +" is not configured with any actions for the ALARM state."'
-# digest: 4a0a00473045022100f3558add899cfc87cef41ebadd1b931c1250bf0f7255e53a67e1aa663b37925b02204010a3c40e8a0ad49ac62d537bcf1a2e4da4d59b40ebc78d5c56e03d1f89348d:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100ec74e58a4ecafde302484c27c761d114bc2c7babcae0491458a94cf6a12acb6d02206af1f79eb9666f2fbd805e82bd2ceb14b75a51fcde66b1105180ff55021ab68a:922c64590222798bb761d5b6d8e72950
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - '"The Amazon CloudWatch " + alarm + " does not have any active actions configured"'
-# digest: 490a0046304402204f22697b5c7a4b568fa37b48600e0f99f469922bdd208491966d4eef4fd6355d02204f33504b85a9de2df430dde270e0f481760be59ca0340bb93c245143558b0444:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100ede2c7feac5d47c4f073d7d85d6334cc220a65dacf1cea096983d1a464343dbc022018c9b15d0dfb8bf7d39afcebf8b0731a790cd21ac2ff470fd5abf2b245ee30a5:922c64590222798bb761d5b6d8e72950
@@ -56,4 +56,4 @@ code:
      - type: dsl
        dsl:
          - '"DMS Multi-AZ  " + replication + " is not enabled"'
-# digest: 4a0a004730450220052c0de2e02b60b42a79e7d02c2e38f90423664ca041b2dddd276b0f0b55d3fa022100a434388c051cee8dfa5e4d962699aa4abdc66971013a62f1cc3c85a9c434519b:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100c67cd0c33238f95b20d5912c1b8800aa69940bb716dd35f2bb8ca66aea1c4ba80221009c7433225fd40509b4a85e2fc696eb64d692e25a530dfbb8b47795c3439d5c46:922c64590222798bb761d5b6d8e72950
@@ -56,4 +56,4 @@ code:
      - type: dsl
        dsl:
          - '"DMS Replication Instances  " + replication + " Publicly Accessible"'
-# digest: 4b0a00483046022100c2e4b02073095257867ae2f880894485ce4395d427a0f5797433d453d16557b4022100f11bea387537d175614dcbe4c0e1f7a3d19cfe18b2eb5177157de179677aaea4:922c64590222798bb761d5b6d8e72950
+# digest: 490a00463044022000b131dbeae740f870eaff7231c7c569dd834c331f38ca46b0991820e3120d95022051094b7224aff719e7e8172873e5598d67fed8b026e4d82ee6370a9921f37230:922c64590222798bb761d5b6d8e72950
@@ -56,4 +56,4 @@ code:
      - type: dsl
        dsl:
          - '"DMS Auto Minor Version Upgrade  " + replication + " not enabled"'
-# digest: 4b0a00483046022100e170aa216555156ddf46a196e60d6985d37d29f32146f0bfeaeef1ceba09e73c022100f95487bc9c2f2bfe9288a9362f868268f3bb7cd963b36c44be1b6629a06b3a6b:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100dd9841e17fd251664e804b43a5ec2e373b4ad37c3321cc3cd980f99ba6078953022100ad38fe36697b3715fd2e059494e8ebc86cc4161dd952eba8a2096a4d3943687d:922c64590222798bb761d5b6d8e72950
@@ -58,4 +58,4 @@ code:
      - type: dsl
        dsl:
          - '"EBS Encryption  " + volumes + " is Disabled"'
-# digest: 4a0a00473045022100fe98ba08fe06c9398f905a0651ac60c5cfbdbeaf2fa0c524aa9d2c0e29d3c75902200ab089e32558f42e2a7f8d5fafb3e309dfe261bad4e417532734222a7cbaa7cf:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100c4371ccc8806720325f44b12c4aaa32e36e59e597932144b8ef05336045bc75f022100b28b86b707ddf220502ef18cdac5a203c14ac7675737101b785fbb923b34d7a4:922c64590222798bb761d5b6d8e72950