Comments on: DISA releases official ESX Security Technical Implementation Guide http://www.intrasection.com/pjmorr/2008/06/04/disa-releases-official-esx-security-technical-implementation-guide/ A home for all things TechnoGeeky Thu, 04 Feb 2010 07:43:52 +0000 http://wordpress.org/?v=abc hourly 1 By: Philip Morrison http://www.intrasection.com/pjmorr/2008/06/04/disa-releases-official-esx-security-technical-implementation-guide/comment-page-1/#comment-207 Philip Morrison Tue, 04 Nov 2008 20:35:13 +0000 http://www.intrasection.com/pjmorr/?p=1200#comment-207 Not sure I understand the question? Not sure I understand the question?

]]> By: Givens http://www.intrasection.com/pjmorr/2008/06/04/disa-releases-official-esx-security-technical-implementation-guide/comment-page-1/#comment-206 Givens Tue, 04 Nov 2008 20:27:00 +0000 http://www.intrasection.com/pjmorr/?p=1200#comment-206 What is this? AS-08-548 Security Technical Implementation Guidance (STIG) What is this?
AS-08-548 Security Technical Implementation Guidance (STIG)

]]> By: Philip Morrison http://www.intrasection.com/pjmorr/2008/06/04/disa-releases-official-esx-security-technical-implementation-guide/comment-page-1/#comment-209 Philip Morrison Wed, 20 Aug 2008 22:41:26 +0000 http://www.intrasection.com/pjmorr/?p=1200#comment-209 So, the process I use is this. 1. Run the DISA provided SRR Unix script. Capture the open issues report. 2. Install LAUS rpm files off of ESX CD Make sure to chkconfig so the service starts at boot service start audit 3. We have another script (unpublished) that changes the banner info based on secret/top secret 4. Run ESX_SRRSecure.sh to lock things down. 5. Reboot 6. Re-run the Unix SRR script. 7. Capture the new open findings report and compare to the first file. As an aside note we also have a corresponding document that goes along with the script to document all the original findings and how to manually fix them or document if they are false positives.... So, the process I use is this.

1. Run the DISA provided SRR Unix script.
Capture the open issues report.
2. Install LAUS rpm files off of ESX CD
Make sure to chkconfig so the service starts at boot
service start audit
3. We have another script (unpublished) that changes the banner info based on secret/top secret
4. Run ESX_SRRSecure.sh to lock things down.
5. Reboot
6. Re-run the Unix SRR script.
7. Capture the new open findings report and compare to the first file.

As an aside note we also have a corresponding document that goes along with the script to document all the original findings and how to manually fix them or document if they are false positives….

]]> By: BacMan http://www.intrasection.com/pjmorr/2008/06/04/disa-releases-official-esx-security-technical-implementation-guide/comment-page-1/#comment-208 BacMan Wed, 20 Aug 2008 01:39:44 +0000 http://www.intrasection.com/pjmorr/?p=1200#comment-208 So, which meant we need to run the ESX SRR script (what is the latest version -1.2?) then run the UNIX script and compare it, right? So, which meant we need to run the ESX SRR script (what is the latest version -1.2?) then run the UNIX script and compare it, right?

]]>