<Past |
Future> |
iLO 2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
iLO 3 |
Divest [2, 3, 4, 5] |
Divest [2, 3, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
iLO 4 |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
iLO 5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.x for iLO 2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
1.x for iLO 3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
2.x for iLO 4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
1.x for iLO 5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
2.x for iLO 5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.x for iLO 5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [2] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [3] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [4] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [5] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [6] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [7] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
Integrated Lights-Out (iLO) version numbers refer to a firmware number that is tied to server model generations and the proper version can be purchased with the server. iLO firmware updates for specific versions are released and available through HP for the lifecycle of the associated hardware.
At the time of writing, versions: 2.33 for iLO 2, 1.94 for iLO 3, 2.81 for iLO 4, 2.78 and 3.05 for iLO 5 are the most current versions released. |