About custom fields - Security Center 5.12

Security Center Administrator Guide 5.12

Product
Security Center
Content type
Guides > Administrator guides
Version
5.12
Language
English
Last updated
2024-10-17

A custom field is a user-defined property associated with an entity type. Custom fields are useful for storing additional information.

Custom fields can include any information that you define. They can use data types that are available by default in Security Center, or you can create your own data types. Once custom fields are added, they are available in all database reports and queries related to the entity they are defined for. If a custom field contains private information, you can restrict its access to certain groups of users. You can also choose to encrypt the custom field values stored the database.

For example, you can add Gender, Home phone number, and Cellphone number as custom fields for cardholder entities, and only allow the Human Resource user group to access that information. To prevent someone with access to the database from viewing this personal information, you can encrypt these custom fields in the database.

Standard data types

Security Center includes the following default data types for custom fields:
Text
Alphanumeric text.
Numeric
Integers in the range -2147483648 to 2147483647.
Decimal
Real numbers from -1E28 to 1E28.
Date
Gregorian calendar date and time.
Boolean
Boolean data, represented by a check box.
Image
Image file. The supported formats are: .bmp, .jpg, .gif, and .png.
Entity
Security Center entity.

Limitations of custom fields

  • Custom fields are always local to the system where they are defined.
    • In a Federation™ scenario, custom fields are not imported from the federated system. However, you can associate custom fields as local attributes to federated entities.
    • In an Active Directory (AD) integration scenario, custom fields can be imported from object attributes to display their values in your local system, but not to update the AD.
  • Encrypted custom fields are subject to the following limitations:
    • You cannot enforce the unique value option if the custom field is encrypted.
    • You cannot use an encrypted custom field as a query filter for reports.

      However, if the client application (Security Desk or Config Tool) is at a version older than 5.10.3.0, encrypted custom fields are displayed as query filters, but they do not work.

    • When you modify the value of an encrypted custom field, the change is recorded in the audit trail, but the old and new values are not shown in the log entry.