CFRipper – CloudFormation Security Scanning and Auditing Tool

usage: [OPTIONS] [TEMPLATES]…

analyze AWS cloud formation template pass through go through Scope. exit code: –

0 = all template Effective and scanned successfully – 1 = Mistake / problem exist

scanning exist At least one template – 2 = exist At least one template Yes no Effective

according to arrive CFRipper (template scanned successfully) – 3 = unknown /

not processed exception exist scanning This template

Options:

—Version exhibit This Version and exit.

—solve / —No–solve solve cloud formation variable and

inherent function [default: False]

—solve–parameter file name JSON/FML document Include key–value right

used for solve cloud formation document and

templating parameter. for example, {“ABC”:

“ABC”} will Change all event of

{“refer to”: “ABC”} exist This cloud formation document arrive

“ABC”.

—Format [json|txt] output Format [default: txt]

—output–folder content if no exhibit, result will Yes send arrive

stdout

—logging [ERROR|WARNING|INFO|DEBUG]

logging grade [default: INFO]

—rule–configure–document file name load rule configure document (type: [.py,

                                  .pyc])

—rule–filter–folder content

all document exist This folder must Yes of type:

[.py, .pyc]

—aws–account–ID text One 12–number AWS account number For example.

123456789012

—aws–headmaster text One comma–divided list of AWS headmaster For example.

Arne:aws:I’m::123456789012:root,234567890123,

Arne:aws:I’m::111222333444:user/user–name

—help exhibit This information and exit.

Read More..