Custom control sets can easily be created and/or bulk uploaded on the controls page of your platform. For existing controls, you also have the ability to apply bulk mapping changes to these controls by uploading a CSV with the control id being the unique key that ties the row to the control in Secureframe. If the ID belongs to an existing control, it will attempt to update the mappings and language of that control. If the ID does not exist, we will create a custom control with the attributes listed in the CSV.  Only custom controls can have their names and descriptions updated.

How to upload a Control CSV

1. Go to the controls page
2. Add custom control > bulk add custom controls
3. Upload CSV or excel file with the controls you would like to create or update - note the required fields in the upload modal
4. Map the applicable columns to the form fields
5. Resolve any formatting issues or error rows
6. Complete!

**note: all mapping additions are additional, you can not destroy mappings in the import

In the event you need to make updates or are not sure exactly how you want to name objects, it’s optional when you want to just map existing controls to framework requirements and only use that aspect of the uploader. For example: 

If you upload a custom control with the following sheet:

and then upload it again with the following:

you can map the custom control to a framework requirement, and if you upload the following:

then you can change the name and description of the existing custom control as seen above.

Mapping Framework Requirements to Controls in a CSV

You can also map existing or new controls to framework requirements in this CSV. All you need to include is a column with the requirement id (or ids separated by commas (without spaces)). Below is where the id is noted in the UI. You will also get the requirement id if you export the framework on the frameworks page.

In the example below, existing control AC-01 will be mapped to requirement CC1.1 in SOC2 and a new custom control named BULK-2 will be mapped to both CC1.1 and CC1.