Using eSecIP you can provision a variety of data to your product’s hardware. The provisioned data requires a set of parameters to define the format and structure, typically grouped together inside the JSON configuration file and referred to as a configuration object belonging to an information type. In every configuration object, parameters define the object's properties. The configuration objects form an information type’s value, as a list.

The parameters are given as colon-separated JSON name/value pairs, referred to as fields and field values in the eSecIP documentation. The name of a field is always a non-empty string in quote marks. Field values can be strings, integers, Boolean values, (configuration) objects, or lists. If a field takes several values, they are comma-separated.

As an example, a product may require several blocks of random data to be provisioned to each device. Each block will require its own configuration object so that the provisioned data is unique for each one. The information type in this example is randomData and its value is a list of randomData configuration objects:

{
  "randomData": [
    {
      "itemName": "random_block_1",
      "size": 512,
      "usageClass": 3,
      "obfuscation": "Obfuscation_3",
      "exportToPR": false
    },
    {
      "itemName": "random_block_2",
      "size": 1024,
      "usageClass": 4,
      "obfuscation": "Obfuscation_1",
      "exportToPR": false
    }
  ]
}