SD Elements supports augmentation and customization of its original content. As teams access the prepared research in application security, a customized layer or organization policy can be added. Non-security domains such as infrastructure security, accessibility, legal requirements, vendor/supply chain management, etc. are also supported.

Content is generally described two ways:

  • Original content: content that SD Elements creates and delivers.

  • Custom content: content that end users create.

SD Elements allows for the customization of the following types of content:

  • Countermeasures, Additional Requirements, and How-tos

    • Markdown is supported, as follows:

    This is how you make a heading (h1,h2,etc):

    # This is a 1st level heading.
    ## This is a 2nd level heading.
    ###### This is a 6th level heading.

    This will produce an unordered list (a blank line is required above and below the list):

    * Red
    * Green
    * Blue

    This will produce an ordered list (a blank line is required above and below the list):

    1. High
    2. Medium
    3. Low

    Code blocks:

        Put four spaces in front of *every* line in your code block.
        Your code will be properly escaped, and will display as a neatly
        formatted code block.

    # You can also wrap the code block using three single quotes and specify a
    # language to use for syntax highlighting (when available).
    function test():
        print("Hello World")

    Put *asterisks* around text you want to emphasize.

    Finally, this is how you make [a hyperlink]( (there
    is no space between the brackets and the parentheses).
  • Weaknesses

  • Project Settings (including sections, subsections, questions and answers)

  • Phases

  • Profiles

Application content becomes relevant and brought into project scope when the project’s settings match the content’s rules. Absent any rules,

  • A Countermeasure appears in a project every time its corresponding Weakness is in-scope.

  • An Additional Requirement appears every time its corresponding Countermeasure is in scope.

  • A How To appears every time its corresponding Countermeasure is in scope.

  • A Countermeasure with the special Weakness "Always Applicable" will appear in every project.

All customization works in the following way:

  • SD Elements ships content by default, which is updated on a periodic basis. Software as a Service (SaaS) / hosted clients receive these updates automatically. On Site Deployment (OSD) administrators must pull updates as they become available.

  • When new custom content is added it appears alongside original content to an end user. There is generally no visible difference except for identification numbers. In the backend, however, custom content is tracked differently than original content. Custom content can be deleted and modified, but the original content cannot be modified or deleted. Countermeasures from original content are an exception: they can be customized and deactivated.

  • When you modify original content, SD Elements keeps a copy of the original version. Your customized version will always take precedence over our version. If we make changes to the original version of content, your modified version will still show up instead of the updated original version. However, you are able to return at any time to the latest original version of content by clicking on "Revert to Original".

New customization features are regularly in our product development roadmap. If you are interested in additional content, please contact your account representative.

results matching ""

    No results matching ""