Adding PCI Flag

README.md

@@ -123,6 +123,7 @@ Some plugins may require additional permissions not outlined above. Since their
 CloudSploit also supports mapping of its plugins to particular compliance policies. To run the compliance scan, use the `--compliance` flag. For example:
 ```
 node index.js --compliance=hipaa
+node index.js --compliance=pci
 ```
 
 CloudSploit currently supports the following compliance mappings:
@@ -131,6 +132,10 @@ CloudSploit currently supports the following compliance mappings:
 
 HIPAA scans map CloudSploit plugins to the Health Insurance Portability and Accountability Act of 1996.
 
+### PCI
+
+PCI scans map CloudSploit plugins to the Payment Card Industry Data Security Standard.
+
 ## Architecture
 
 CloudSploit works in two phases. First, it queries the AWS APIs for various metadata about your account. This is known as the "collection" phase. Once all the necessary data has been collected, the result is passed to the second phase - "scanning." The scan uses the collected data to search for potential misconfigurations, risks, and other security issues. These are then provided as output.

index.js

@@ -46,9 +46,13 @@ if (process.argv.join(' ').indexOf('--compliance') > -1) {
     if (process.argv.join(' ').indexOf('--compliance=hipaa') > -1) {
         COMPLIANCE='hipaa';
         console.log('INFO: Compliance mode: HIPAA');
+    } else if (process.argv.join(' ').indexOf('--compliance=pci') > -1) {
+        COMPLIANCE='pci';
+        console.log('INFO: Compliance mode: PCI');
     } else {
         console.log('ERROR: Unsupported compliance mode. Please use one of the following:');
         console.log('       --compliance=hipaa');
+        console.log('       --compliance=pci');
         process.exit();
     }
 }