Master

.dockerignore

@@ -0,0 +1,5 @@
+.*
+Dockerfile
+docs
+LICENSE
+README.md

.eslintrc.json

@@ -20,7 +20,6 @@
         "helpers/google/functions.js",
         "helpers/oracle/functions.js",
         "plugins/github/",
-        "plugins/google/",
         "plugins/oracle/",
         "*.spec.js"
     ],
@@ -50,6 +49,19 @@
         ],
         "no-eval": [
             "error"
+        ],
+        "keyword-spacing": [
+            "error",
+            {
+                "before": true
+            }
+        ],
+        "brace-style": [
+            "error",
+            "1tbs",
+            {
+                "allowSingleLine": true
+            }
         ]
     }
 }

.github/CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
-# CloudSploit Code of Conduct
+# CloudExploit Code of Conduct
 
 ## Our Pledge
 
@@ -55,7 +55,7 @@ a project may be further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at support@cloudsploit.com. All
+reported by contacting the project team at support@khulnasoft.com. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.

.github/CONTRIBUTING.md

@@ -1,14 +1,14 @@
-# Contributing to CloudSploit
-Thank you for your interest in contributing to CloudSploit! We welcome your PRs, issues, feedback, and other contributions to this open source repository. To keep things moving smoothly, please use the following guidelines when working with the CloudSploit source code.
+# Contributing to CloudExploit
+Thank you for your interest in contributing to CloudExploit! We welcome your PRs, issues, feedback, and other contributions to this open source repository. To keep things moving smoothly, please use the following guidelines when working with the CloudExploit source code.
 
 ## Code of Conduct
-The CloudSploit project, maintainers, and contributors are governed by the [CloudSploit Code of Conduct](CODE_OF_CONDUCT.md). By contributing, you are agreeing to uphold this code in your interactions with the CloudSploit community.
+The CloudExploit project, maintainers, and contributors are governed by the [CloudExploit Code of Conduct](CODE_OF_CONDUCT.md). By contributing, you are agreeing to uphold this code in your interactions with the CloudExploit community.
 
 ## License
-By contributing code to CloudSploit, you attest that you have the rights to all code and that you are assigning these rights to Khulnasoft Security, Ltd. for use within its projects.
+By contributing code to CloudExploit, you attest that you have the rights to all code and that you are assigning these rights to KhulnaSoft Security, Ltd. for use within its projects.
 
 ## Getting Started
-Please read our [README](../README.md#installation) for information on getting setup to use and develop CloudSploit scans locally. We also have a [guide for writing new plugins](../docs/writing-plugins.md).
+Please read our [README](../README.md#installation) for information on getting setup to use and develop CloudExploit scans locally. We also have a [guide for writing new plugins](../docs/writing-plugins.md).
 
 ## Proposing Large Changes
 While we welcome all contributions, large pull requests that make significant changes to the codebase are difficult to review are merge without prior discussion. Please open an issue to discuss these changes before beginning work on them.

.github/workflows/scans_ci.yml

@@ -0,0 +1,25 @@
+name: 
+on: [push, pull_request, create, delete, issue_comment]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - uses: codespell-project/actions-codespell@master
+        with:
+          check_filenames: true
+          skip: ./.github/*,.git,./package.json,./package-lock.json,./node_modules,./tests,./config,*.png,Dockerfile,./scripts,*.spec.js,./plugins/azure/storageaccounts/storageAccountsAADEnabled.js,./plugins/aws/cloudtrail/cloudtrailBucketAccessLogging.js,./helpers/google/index.js,*zip
+          ignore_words_list: iam,\"tRe\",AKS,aks,optin,callInt,callInt
+      - run: npm install
+
+      - name: Lint
+        run: npm run lint
+
+      - name: NPM Test
+        run: npm test

.gitignore

@@ -9,4 +9,5 @@ vscode/*
 .idea
 coverage/
 .nyc_output
-config.js
+config.js
+package-lock.json

.travis.yml

@@ -14,7 +14,7 @@ jobs:
     - stage: Lint
       script: npm run lint
     - stage: NPM release
-      # Deployment of cloudsploit is setup to work nicely both for the master repo
+      # Deployment of cloudexploit is setup to work nicely both for the master repo
       # any forks. That is, a fork can also publish to NPM to a custom scope. To do
       # this, you need to do the following in the Travis CI settings for your account
       #
@@ -42,7 +42,7 @@ jobs:
       before_deploy:
         # You need to create a variable in your Travis CI settings to provide the
         # npm package scope. This allows forks to publish under their own name.
-        - sed -i 's#"cloudsploit"#"'$NPM_SCOPE'cloudsploit"#g' package.json
+        - sed -i 's#"cloudexploit"#"'$NPM_SCOPE'cloudexploit"#g' package.json
       deploy:
         # We modify package.json to change the package name automatically, so
         # don't to cleanup otherwise that would revert the package name change.
@@ -61,18 +61,18 @@ jobs:
       #
       # 2. Similarly, add an environment variable with your DOCKER_PASSWORD
       #
-      # 3. If you want to install a different version of cloudsploit in the container
+      # 3. If you want to install a different version of cloudexploit in the container
       #    (for example because you are building a fork), then set DOCKER_NPMPACKAGENAME
-      #    to the name of NPM package you want to install, for example @myscope/cloudsploit
+      #    to the name of NPM package you want to install, for example @myscope/cloudexploit
       #
       # There is probably a strong relationship between NPM_SCOPE and DOCKER_NPMPACKAGENAME
       # but that's up for you in Travis CI to define.
       if: env(DOCKER_USERNAME) AND env(DOCKER_PASSWORD)
       script:
-      - DOCKER_BUILD_NPMPACKAGENAME="${DOCKER_NPMPACKAGENAME:-cloudsploit}"
+      - DOCKER_BUILD_NPMPACKAGENAME="${DOCKER_NPMPACKAGENAME:-cloudexploit}"
       - echo "Creating docker image from NPM package ${DOCKER_NPMPACKAGENAME}"
       - echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
-      - docker build --build-arg PACKAGENAME=$DOCKER_BUILD_NPMPACKAGENAME -t cloudsploit-scans .
+      - docker build --build-arg PACKAGENAME=$DOCKER_BUILD_NPMPACKAGENAME -t cloudexploit-scans .
       - docker images
-      - docker tag cloudsploit-scans $DOCKER_USERNAME/cloudsploit-scans
-      - docker push $DOCKER_USERNAME/cloudsploit-scans
+      - docker tag cloudexploit-scans $DOCKER_USERNAME/cloudexploit-scans
+      - docker push $DOCKER_USERNAME/cloudexploit-scans

Dockerfile

@@ -1,27 +1,38 @@
-FROM node:8-alpine
+FROM node:lts-alpine3.12
 
 # Define a build argment that can be supplied when building the container
 # You can then do the following:
 #
-# docker build --build-arg PACKAGENAME=@myscope/cloudsploit
+# docker build --build-arg PACKAGENAME=@myscope/cloudexploit
 #
 # This allows a fork to build their own container from this common Dockerfile.
 # You could also use this to specify a particular version number.
-ARG PACKAGENAME=cloudsploit
+ARG PACKAGENAME=cloudexploit
 
-# Install cloudsploit/scan into the container using npm from NPM
-RUN mkdir /var/scan \
-&& cd /var/scan \
-&& npm init --yes \
-&& npm install ${PACKAGENAME}
+# Create a non-root user and group
+RUN addgroup -S cloudexploit && adduser -S cloudexploit -G cloudexploit
 
-# Setup the container's path so that you can run cloudsploit directly
+COPY . /var/scan/cloudexploit/
+
+# Set the working directory to /var/scan
+WORKDIR /var/scan
+
+# Install cloudexploit/scan into the container using npm from NPM
+RUN npm init --yes \
+&& npm install ${PACKAGENAME} \
+&& npm link /var/scan/cloudexploit \
+&& chown -R cloudexploit:cloudexploit /var/scan
+
+# Setup the container's path so that you can run cloudexploit directly
 # in case someone wants to customize it when running the container.
 ENV PATH "$PATH:/var/scan/node_modules/.bin"
 
+# Switch to non-root user
+USER cloudexploit
+
 # By default, run the scan. CMD allows consumers of the container to supply
 # command line arguments to the run command to control how this executes.
 # Thus, you can use the parameters that you would normally give to index.js
 # when running in a container.
-ENTRYPOINT ["cloudsploitscan"]
+ENTRYPOINT ["cloudexploit"]
 CMD []