Filter
Top Products
Chapter 8. Remediation subsystem implementation 405
The attributes that are generated by the Security Compliance Manager client are
always present, and are known as innate attributes. These attributes, presented
in Table 8-7, cannot be overridden by user settings.
Table 8-7 Innate remattribute tag usage
All other attributes come from either the HANDLER_ATTRIBUTES parameter of
the policy collector or the local handlers.properties file. In both of these locations
attributes are specified in key-value pairs, separated by an equals sign (=). In
general, attributes are used to control the configuration and behavior of the
remediation subsystem, but they can also be used to provide general
Attribute Example Description
client.alias scmclient The client's alias. This may be null if
the client is not a DHCP client
client.dhcp false Indicates whether the client is a DHCP
client.
client.fingerprint a3:55:e5:62:2a:db:52:93:
3b:c2:22:38:44:53:bf:02
The client's globally unique fingerprint.
client.id 1 The client's unique identifier as set by
the server.
client.root C:\PROGRA~1\IBM\SC
M\client
The root of the client installation.
os.arch x86 The processor architecture of the client
as reported by Java.
os.name Windows 2000 The host OS name as reported by
Java.
os.version 5.0 The host OS version as reported by
Java.
win.build 2195 The build version of Windows as
reported in the CurrentBuildNumber
registry key.
win.product Microsoft Windows 2000 The name of the Windows product as
reported in the ProductName registry
key
win.sp Service Pack 4 The Service Pack of the Windows
product as reported in the CSDVersion
registry key.
win.version 5.0 The version of Windows as reported in
the CurrentVersion registry key.