Working with custom fields

Custom Fields give you a way to extend Trust Protection Foundation’s out-of-the-box capabilities to capture data points that are not part of the standard trust protection lifecycle and may be unique to your environment.

Being able to store additional data allows Trust Protection Foundation to become more tightly aligned with your internal business processes without requiring any custom software development. Custom fields can also be used to correlate Trust Protection Foundation objects with non-Trust Protection Foundation infrastructure whether it's a manual process or integration between applications.

The ability to add custom fields gives you:

  • A place to store arbitrary data related to assets that Trust Protection Foundation is already tracking
  • A way to better align Trust Protection Foundation with customer-specific business processes
  • A basis for correlating Trust Protection Foundation assets with external infrastructure
  • A way to collect additional data from certificate managers about their assets

EXAMPLE  Let's say that you want to be able to track your certificates by Location or Cost Center. You can create custom fields called Location and Cost Center that can be applied to certificates or devices. When you need to, you can export the data or view a report that shows you certificates and devices that use Location and Cost Center.

NOTE  Only CyberArk's Symantec Managed PKI for SSL and Entrust Certificate Services drivers support vendor custom fields. If you want to use custom fields, we recommend using CyberArk's custom fields feature. To ensure a smooth ride, either ensure that all custom fields for your chosen vendor are optional and use CyberArk's custom fields instead, or use one of CyberArk's custom field-supported drivers (Symantec or Entrust).

TIP  To browse topics in this section, use the menu on the left side of this page.