├── DFLabs Github Software Programs License Agreement 08-06-18.pdf ├── NAT User Manual.pdf ├── NAT.exe ├── README.md ├── default.ini └── sample.cmd /DFLabs Github Software Programs License Agreement 08-06-18.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dflabs/NAT/083a152849a7b2523c80334eb853ab65ffb6c62d/DFLabs Github Software Programs License Agreement 08-06-18.pdf -------------------------------------------------------------------------------- /NAT User Manual.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dflabs/NAT/083a152849a7b2523c80334eb853ab65ffb6c62d/NAT User Manual.pdf -------------------------------------------------------------------------------- /NAT.exe: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dflabs/NAT/083a152849a7b2523c80334eb853ab65ffb6c62d/NAT.exe -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # No-Script Automation Tool 2 | The No-Script Automation Tool (NAT) was designed to solve the complexity and management issues surrounding scripting multiple tools via batch files or other scripting languages for Windows systems. NAT allows users to run sets of pre-defined and pre-verified tools based on user specified input, pre-defined commands and system properties such as architecture and Windows version. 3 | 4 | NAT may be used freely for non-commercial purposes, without warrant or support, as outline in the DFLABS GITHUB SOFTWARE PROGRAMS LICENSE AGREEMENT. 5 | 6 | Usage: 7 | 8 | -h Display help menu and exit 9 | 10 | -x Bypass integrity check 11 | 12 | -c Create integrity check file 13 | 14 | -i Use the specified .ini file (default is default.ini) 15 | -------------------------------------------------------------------------------- /default.ini: -------------------------------------------------------------------------------- 1 | Process 2 | Network 3 | Users 4 | OS 5 | File System 6 | -------------------------------------------------------------------------------- /sample.cmd: -------------------------------------------------------------------------------- 1 | # Any lines beginning with the # symbol will be ignored. 2 | # 3 | # Specify one set of command line arguments per line. 4 | # 5 | # Make sure to end the last set of command line arguments with a newline character, or it will not be executed. 6 | # 7 | # By default, output from each tool will be piped to a text file in the specified output directory. 8 | # To prevent this for a specific tool, use the variable %NOOUT% as the sole argument in that tool's .cmd file, 9 | # or at the end of each line of command line arguments if other arguments are specified. 10 | # This may be useful if the output directory is specified as part of the command line arguments for the tool. 11 | # 12 | # To specify the output directory as part of the command line arguments. Use the variable %OUTDIR% in place of the 13 | # output directory. This variable will be dynamically replaced with the correct output directory each time the 14 | # tool is executed. For example, "-o %OUTDIR%\output.txt" for mytool.exe will result in the command... 15 | # "mytool.exe -o \output.txt being executed at runtime. --------------------------------------------------------------------------------