Dynamic Code Finding Data Model
The Dynamic Code Finding data model represents a security finding using the Dynamic Application Security Testing (DAST) methodology. It extends the Finding data model.
The following table details the default attributes of the Dynamic Code Finding data model:
Order | Attribute Name | Attribute Type | Relationship Type | Required |
---|---|---|---|---|
1 | displayName | Calculated (Text) | N/A | Yes |
2 | type | Reference (Dynamic code finding definition) | IS | No |
3 | url | Text | N/A | No |
4 | path | Text | N/A | No |
5 | assessment | Reference (Assessment) | DISCOVERED_IN | No |
6 | baseRiskScore | Calculated (Number) | N/A | No |
7 | riskFactorOffset | Calculated (Number) | N/A | No |
8 | riskScore | Calculated (Number) | N/A | No |
9 | riskRating | Calculated (Single Choice) | N/A | No |
10 | ageinDays | Calculated (Number) | N/A | No |
11 | sla | Calculated (Number) | N/A | No |
12 | slaLevel | Calculated (Text) | N/A | No |
13 | dueDate | Calculated (Date Time) | N/A | No |
14 | complianceStatus | Calculated (Single Choice) | N/A | No |
15 | daysToFix | Calculated (Number) | N/A | No |
16 | confidence | Single Choice | N/A | No |
17 | summary | Text | N/A | No |
18 | description | Text | N/A | No |
19 | severity | Single Choice | N/A | No |
20 | status | Status | N/A | No |
21 | results | Text | N/A | No |
22 | statusCategory | Single Choice | N/A | No |
23 | targets | Reference (Asset) | HAS | No |
24 | remediationSLA | Number | N/A | No |
25 | firstFound | Date Time | N/A | No |
26 | lastFound | Date Time | N/A | No |
27 | lastFixed | Date Time | N/A | No |
28 | extendedDueDate | Date Time | N/A | No |
29 | riskOwner | Category | N/A | No |
30 | remediationOwner | Category | N/A | No |
31 | riskScoringModel | Risk Scoring Model | N/A | No |
32 | riskFactors | Risk Factors | N/A | No |
33 | slaDefinition | SLA | N/A | No |
34 | uid | Text | N/A | Yes |
35 | name | Text | N/A | Yes |
36 | dataModelName | Calculated (Text) | N/A | No |
37 | sourceUids | Text (Multivalued) | N/A | No |
38 | connectorCategories | Text (Multivalued) | N/A | No |
39 | connectorNames | Text (Multivalued) | N/A | No |
40 | dataIntegrationTitles | Text (Multivalued) | N/A | No |
41 | sourcesIcons | Source data models icons | N/A | No |
42 | flowState | Text | N/A | No |
43 | sources | Reference (Base model) | SOURCED_FROM | No |
44 | dateCreated | Date Time | N/A | No |
45 | lastUpdated | Date Time | N/A | No |
46 | createdBy | Text | N/A | No |
47 | updatedBy | Text | N/A | No |
48 | categories | Text (Multivalued) | N/A | No |
FOOTNOTES
- The Order column specifies the order of attributes being calculated in data computation.
- The attribute names are used in Brinqa Query Language (BQL) queries and Brinqa Condition Language (BCL) predicates.
- In the Type column, Calculated means that the value of the attribute is computed by executing a script. The text in the parentheses after Calculated denotes the type of the outcome.
- In the Type column, Reference means that two data models are related. The name in the parentheses after Reference indicates the other data model.
- The Relationship Type column only applies to the Reference type attributes. You can use the relationship type keyword in BQL queries.