Static Code Finding Data Model
The Static Code Finding data model represents a security finding identified using the Static Application Security Testing (SAST) methodology. It extends the Finding data model.
The following table details the default attributes of the Static Code Finding data model:
Order | Attribute Name | Attribute Type | Relationship Type | Required |
---|---|---|---|---|
1 | displayName | Calculated (Text) | N/A | Yes |
2 | type | Reference (Static code finding definition) | IS | No |
3 | languages | Text (Multivalued) | N/A | No |
4 | fileName | Text | N/A | No |
5 | method | Text | N/A | No |
6 | codeSnippet | Text Area | N/A | No |
7 | assessment | Reference (Assessment) | DISCOVERED_IN | No |
8 | baseRiskScore | Calculated (Number) | N/A | No |
9 | riskFactorOffset | Calculated (Number) | N/A | No |
10 | riskScore | Calculated (Number) | N/A | No |
11 | riskRating | Calculated (Singe Choice) | N/A | No |
12 | ageInDays | Calculated (Number) | N/A | No |
13 | slaLevel | Calculated (Text) | N/A | No |
14 | sla | Calculated (Number) | N/A | No |
15 | dueDate | Calculated (Date Time) | N/A | No |
16 | complianceStatus | Calculated (Singe Choice) | N/A | No |
17 | daysToFix | Calculated (Number) | N/A | No |
18 | confidence | Single Choice | N/A | No |
19 | summary | Text | N/A | No |
20 | description | Text | N/A | No |
21 | severity | Single Choice | N/A | No |
22 | status | Status | N/A | No |
23 | results | Text | N/A | No |
24 | statusCategory | Singe Choice | N/A | No |
25 | targets | Reference (Asset) | HAS | No |
26 | remediationSLA | Number | N/A | No |
27 | firstFound | Date Time | N/A | No |
28 | lastFound | Date Time | N/A | No |
29 | lastFixed | Date Time | N/A | No |
30 | extendedDueDate | Date Time | N/A | No |
31 | riskOwner | Category | N/A | No |
32 | remediationOwner | Category | N/A | No |
33 | riskScoringModel | Risk Scoring Model | N/A | No |
34 | riskFactors | Risk Factors | N/A | No |
35 | slaDefinition | SLA | N/A | No |
36 | uid | Text | N/A | Yes |
37 | dataModelName | Calculated (Text) | N/A | No |
38 | sourceUids | Text (Multivalued) | N/A | No |
39 | connectorCategories | Text (Multivalued) | N/A | No |
40 | connectorNames | Text (Multivalued) | N/A | No |
41 | dataIntegrationTitles | Text (Multivalued) | N/A | No |
42 | sourcesIcons | Source data models icons | N/A | No |
43 | name | Text | N/A | No |
44 | categories | Text (Multivalued) | N/A | No |
45 | flowState | Text | N/A | No |
46 | sources | Reference (Base model) | SOURCED_FROM | No |
47 | dateCreated | Date Time | N/A | No |
48 | lastUpdated | Date Time | N/A | No |
49 | createdBy | Text | N/A | No |
50 | updatedBy | Text | 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.