In contrast to other scripting languages, the Terminal session launched by AppleScript runs in the user’s home directory by default, not in the current working directory. Note: the location where you save the AppleScript file is less important than the JavaFX and STIGViewer files. I saved it in the same directory as my JavaFX and STIGViewer JAR for the sake of simplicity, but you can save it wherever.
This will take a lot of the difficult management of multiple checklists and automate it and provide report against all of the information, so you can see your “system” as a whole or drill down to the individual checklist and STIG.Name your script - I chose the very original LaunchSTIGViewer and choose where to save it. ckl “checklist” file(s) to upload into OpenRMF which is a fantastic tool that can assist you with managing hundreds of these individual checklist files for you network environment as a whole. The point is the number of checklists you have to manage can get extremely cumbersome. For an example one server may have Windows Operating system checklist, Internet Explorer checklist, DotNet checklist, Windows Firewall checklist…….
If you would like to manage many checklists such as 10, 50, 100 ……depending on the size of your environment you may want to take your files you have created and upload them into the OpenRMF tool. You can do this for one checklist at a time. You have to import for each type, then create a checklist from each import, and then edit each individual V-xxxx with the status and make sure you save after each time so you don’t lose data. There are few unfortunate issues with the STIG Viewer app. You can keep moving forward and edit the checklist as needed and add and create more.
0 kommentar(er)
