With Secureframe, users can create custom frameworks and utilize Secureframe's Test Library for your organization's security program. Users can customize sections, requirements and map custom or existing controls to make Secureframe the single source of truth for all compliance needs.
Structuring your CSV for import
Here are the headers that could exist in your CSV:
Section1:name: Required
Section2:name: Optional for nested sections
Section3:name:Optional for nested sections
Section4:name: Optional for nested sections
FrameworkRequirement:key: Required ; must be unique
FrameworkRequirement:name: Required
FrameworkRequirement:description: Required
The custom frameworks CSV should follow the exact same structure as you see below. Each row should be a distinct framework requirement that is mapped to its parent section and subsections. If you have different columns, you can always map the columns to the relevant fields using our CSV upload UI:
Creating Custom Frameworks
If you don't see the custom framework enabled, please check with your Customer Success Manager at [email protected]
Navigate to the Frameworks tab.
Click Add Custom Framework in the top right corner.
In the modal that appears, enter a Framework Name. (You may enter up to 50 characters
(Optional) Enter a Tag.
Tags are used to organize and identify frameworks throughout the platform. (ex, Framework & Control pages)
A tag is required if the framework name exceeds 32 characters.
Framework tags are visible across the platform in test mapping views and filtering, making it easier to locate and manage tests by framework (see example below).
Upload your CSV file structured with the correct column headers. (Custom framework template here)
Mapping Controls to your Custom Framework
Once you have uploaded your new Custom Framework, you can now start mapping controls to your custom framework's requirements.
To learn more about how to map controls, visit our full guide here.