Update README with procedures.

Author: explodeo

README.md

@@ -4,7 +4,17 @@ This project creates provides a couple utilities that culminate in a shrunken-do
 
 It's annoying that without any of the paid options by Tenable, I can't have a monolithic config file that instantiates scans, and imports credentials into a policy file.
 
-**This fixes that**
+***This fixes that***
+
+The only thing you still have to do is install or rebuild plugins (useful for troubleshooting):
+
+```sh
+# Install new plugins
+$ nessuscli update PLUGINS.tar.gz
+
+# Recompile plugins manually
+$ nessusd -R
+```
 
 ## NessusAPI
 
@@ -13,13 +23,27 @@ An extension of the [pyTenable](https://github.com/tenable/pyTenable) library fo
 ### [`nessusapi.py`](src/NessusAPI/nessusapi.py)
 The [nessusapi](src/NessusAPI/nessusapi.py) implements a few methods, namely `import_policy()` and `add_credentials()` which send a PUT/POST request to the Nessus backend API to add credentials to a specific policy.
 
+The [`example-config.json`](src/NessusAPI/configs/example-config.json) is an example config file. The `credentials` object inside it closely mimics the PUT request data that Nessus executes when it adds credentials to a policy file.
+
 ### [`nessus-configure.py`](src/NessusAPI/nessus-configure.py)
 Creates a `Nessus` API instance using [`pyTenable`](https://github.com/tenable/pyTenable) and loads Policies/Credentials and scans in using a passed `config.json` 
 
-The [`example-config.json`](src/NessusAPI/configs/example-config.json) is an example config file. The `credentials` object inside it closely mimics the PUT request data that Nessus executes when it adds credentials to a policy file.
+```sh
+
+# Load the Policies/Configs into Nessus
+$ nessus-configure -i /path/to/config.json
+
+# Export Complete or Imported Scans
+$ nessus-configure -e /path/to/config.json
+
+# You can also programatically interact with nessus:
+$ nessus-configure --interactive /path/to/config.json
+```
+**TODO:** Update nessus-configure to pass args to allow exporting as pdf and csv with all columns.
 
 ***NOTE:*** I have a TODO to document the code properly later -- this was a rush job needed for another project of mine.
 
+
 ## "TenableCore" Imitation
 
 This is broken into a couple parts. 
@@ -31,8 +55,23 @@ This is broken into a couple parts.
 ## NetworkCtl
 
 A small utility script that wraps `nmcli` to clear, list, and load network profiles.</br>
+All you need to do is create a `*.nmconnection` file manually or with `nmtui` and put it in `./TenableCore/NetworkManager` and the `build.sh` will install it with permissions: `rw------- root:root /etc/NetworkManager/system-connections/*.nmconnection` 
+
+Make sure the syntax is good otherwise it won't load.
+
 The main benefit here is `networkctl load PROFILE` will load all profiles starting with `PROFILE` -- a useful utility for loading an interface and all its VLANs simultaneously. 
 
+```sh
+# list connection profiles (nmcli con show)
+$ networkctl list
+
+# restart networking only loading connections starting with the name eth0_vlan
+$ sudo networkctl load eth0_vlan
+
+# clear all network connection profiles
+$ sudo networkctl clear
+```
+
 ***
 
 ## Build Process
@@ -42,15 +81,13 @@ This is currently in process to be **fully** automated
 Recreate distribution files and `scp` them to the VM:
 ```sh
 $ ./build.sh
-$ scp ./dist/installer/* root@192.168.56.101:/tmp
+$ scp ./dist/installer/* root@192.168.56.101:/opt
 ```
 
 Log into the VM and install/configure ACAS:
 ```sh
-$ su root
-# cd /tmp
-# chmod 700 ./build_tenablecore.sh
-# ./build_tenablecore.sh
+$ cd /opt
+$ sudo ./build_tenablecore.sh
 ```
 
 Watch the prompts in the output to:
@@ -70,10 +107,25 @@ Remove the build script:
 Once complete, copy the VM virtual disk into `./dist/vm/`. Pack this entire folder to make the portable installation. </br>
 You can compress the VM and copy the archive instead using this example: 
 ```sh
-$ tar -czvf ./dist/vm/TenableCore.tar.gz -C "~/VirtualBox VMs/TenableCore" TenableCore.vmdk
+$ tar -czvf ./dist/vm/TenableCore.tar.gz -C "~/VirtualBox VMs/TenableCore" TenableCore.vdi
 ```
 
 ***
 ***
 
+## Test Setup
+
+Note that the purpose of this VM is to scan things on-demand --- as in you plug it in, scan, export, and delete it.
+
+- VirtualBox 7.1
+- 8 GB RAM
+- 4 Threads
+- No usb, shared folders, or audio
+- No optical/floppy drives
+
+The VM in use is Oracle 9.4 with the Unbreakable Enterprise Kernel (UEK). <br>
+I install using LVM Thin Partitioning on a 20GB disk. KDump is turned off with no security policy enabled.
+
+***
+
 **Side Note:** *I should **probably** rename this to ACAS-API since it's more fitting and I don't want to get sued by Tenable*

build.sh

@@ -44,7 +44,7 @@ function usage_all(){
     echo '  ./build.sh install TODO'
 }
 
-function build_tar_dist(){
+function build_tar_local_installer(){
     # The final TGZ and install script is outputted into the ./dist folder
     mkdir -p ./dist/installer
 
@@ -66,12 +66,6 @@ function build_tar_dist(){
         cp ./install/utils/build_tenablecore.sh ./dist/installer
 }
 
-function build_vmdk(){
-    # build vm with base image option
-    # mkdir -p ./dist/vm
-    echo 'TODO: NOT IMPLEMENTED'    
-}
-
 function build_vm_dist(){
     # cp ./install/utils/TenableCore.sh ./dist/vm/
     # tar -czvf ./dist/vm/TenableCore.tar.gz -C "~/VirtualBox VMs/TenableCore" TenableCore.vmdk
@@ -102,4 +96,4 @@ function build_vm_dist(){
 # esac
 
 
-build_tar_dist
+build_tar_local_installer