Question & Answer
Question
What is the naming scheme for Guardium agents/modules (STAP, KTAP, CAS, GIM & Discovery)?
Cause
Lack of documentation on Guardium agent/module naming scheme.
Answer
A] Naming scheme for all agents/modules in v9.0 and v9.1 prior to release of GPU 500 is as follows:
STAP agent:
InfoSphere_Guardium_S-TAP_<OS>_<MajorVer>_<Revision>
Example:
InfoSphere_Guardium_S-TAP_Red_Hat_9.1_r71327
KTAP module:
guard-STAP-<MajorVer>_<InternalBuildVer>-<OSVer-Architecture>_<Revision>_<BuildDate>
Example:
guard-STAP-9.0.0v90_3-rhel-5-linux-x86_64_r71327_2015-02-20
CAS agent:
InfoSphere_Guardium_CAS_<OS>_<MajorVer>_<Revision>
Example:
InfoSphere_Guardium_CAS_Windows_9.1_r56624
Unix GIM & Discovery module:
InfoSphere_Guardium_GIM_and_Discovery_<OS>_<MajorVer>_<Revision>
Example:
InfoSphere_Guardium_GIM_and_Discovery_Red_Hat_9.1_r71327
Windows GIM:
InfoSphere_Guardium_GIM_<OS>_<MajorVer>_<Revision>
Example:
InfoSphere_Guardium_GIM_Windows_9.1_r60431
B] Naming scheme for all agents/modules released post GPU 500 release (including v8.2 agents/modules) is as follows:
Guardium_[argument1]_[argument2]_[argument3]_]_[argument4]_[argument5]_]_[argument6]_[argument7]
[argument1] = Guardium version number, examples - 8.2, 9.0, 9.1, 9.5, 10
[argument2] = Name of agent, examples- STAP, ATAP, KTAP, CAS, GIM, GIM-DISCOVERY, FAM
[argument3] = Name of operating system, examples - RedHat, Suse, zLinux, Ubuntu, Solaris, AIX, HPUX, Windows
[argument4] - Optional - version of operating system installed on
[argument5] -Optional - topography, x86_64, i686, etc.
[argument6] = Build version, example - r71327
[argument7] - Optional - additional information (for example, add a date for KTAP)
Examples -
STAP agent:
Guardium_9.5_S-TAP_Suse_r73521
KTAP module:
Guardium_KTAP_8.2_suse-11-linux-x86-64_r45364_2015-03-30
CAS agent:
Guardium_9.5_CAS_Suse_rxxxxx
Unix GIM & Discovery module:
Guardium_9.5_GIM-Discovery_RedHat_r73521
Windows GIM:
Guardium_9.5_GIM_Windows_r73464
Note:
1) There is no Discovery module for Windows.
2) The agent/module naming scheme was standardized in Guardium v9. However, v8.2 agents/modules released post v9 GPU 500 release will follow this naming convention.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21698858