Notes on intentionally Air-Gapping an IEM Installation

From RiceFamily Wiki
Revision as of 14:59, 13 February 2015 by Rice0009 (Talk | contribs)

Jump to: navigation, search

Premise

We need to install IEM in such a way that it cannot automatically update content from IBM.

Reasons

  • Strict adherence to ITIL Change Management Controls.
  • Requirement that even though IBM is actively developing the OS Deployment abilities in IEM, our group that Manages Workstation/Laptop images is insisting on a stable environment.

IBM Documentation Links

Random Thoughts

From reading the IBM Documentation, it looks like the assumption with an Air-Gapped environment is that the server is not able to access the Internet at all, thus it cannot access neither the IBM Fixlet content not the Vendor Patch content itself.

What I'm going to be trying to do is 'trick' the server into thinking that it cannot find the server that hosts the IBM Fixlet Content, but leave it able (hopefully) to access the actual Patch content from the Vendors sites.

I believe that all I need to do is create an entry in the 'hosts' file that redirects the sites below to 127.0.0.1 or some other address where the server cannot find the IBM Fixlet content.

Utilities

  • Air-Gap.exe tool

Procedures