Currently, DISA's (https://cyber.mil) latest 2.X version of STIGViewer is not supported on OS X. For a lot of us Mac users, this means finding other means or workarounds, such as installing a Virtual Machine (VM) to meet the DoD STIG requirements.
- Go to the Releases page
- Download the latest
STIG Viewer 2_18.zipfile - Extract the zip file to your Applications folder or desired location
Because this application is not signed by Apple, you'll need to allow it to run:
- After extracting, right-click (or Control-click) on STIG Viewer.app
- Select Open from the context menu
- Click Open in the security dialog that appears
- The application will now launch and be trusted for future use
Alternatively, you can allow it through System Settings:
- Go to System Settings > Privacy & Security
- Scroll down to the Security section
- Click Open Anyway next to the STIG Viewer message
- Confirm by clicking Open
Example: A couple years ago, DISA released newer versions of STIGs with updated Vulnerability Identification (V-ID) numbers and also a new version of STIGViewer.
Without using that newer version of STIGViewer, the updated V-IDs could not be seen.
Additionally, Security Content Automation Protocols (SCAPs) could not sucuessfully map to previous or legacy V-IDs without using the most up-to-date STIG Viewer.
While this may be a small or minusucle example, having the most up-to-day STIGViewer is important for overall accuracy.
Using Cursor IDE to leverage AI, the program was prompted to use the existing Linux and Windows OS new 2.18 version, to recreate it for Mac OS X .dmg.
Fully functional meaning creating, importing, exporting, saving, etc.
Because I am not the originator of STIGViewer, this application is not signed with an Apple Developer certificate. This will cause macOS to show a security warning on first launch. Follow the installation instructions above to bypass this warning.
Security warning example:
How to allow the application:
- macOS 10.15 (Catalina) or later
- Apple Silicon (M1/M2/M3) or Intel processor
- Approximately 200MB of disk space
For issues or questions, please open an issue on the GitHub repository.