9.0 GraphQL Changes¶

With VECTR 9.0 some breaking changes have been made to the GraphQL API. See the listing below.

Fields No Longer Supported¶

The fields in the list below are deprecated and no longer supported. They will be removed at some point in the future.

Deprecated Type Fields¶

Type	Field
DefensiveLayer	`deprecated`
KillChain	`tags`
Organization	`tags`
Phase	`tags`
Source	`tags` `phases`
Target	`tags` `phases`
TestCase	`activityLogged` `alertSeverity` `outcomes` `redTeamMetadata` `blueTeamMetadata`
RedTool	`tags` `phases`
Target	`tags` `phases` `vendor`

Deprecated Input Fields¶

The CreateTestCaseDataInput fields in the list below will map to outcomePath using the best guess

CreateTestCaseDataInput.outcome
CreateTestCaseDataInput.alertSeverity
CreateTestCaseDataInput.alertTriggered
CreateTestCaseDataInput.activityLogged
CreateTargetDataInput.phases
CreateSourceDataInput.phases

Changes to Response Values¶

Affected Field	Previous Value	New Value
TimelineEvent.fieldName	`status` `outcomeId`	`to_status` `to_status`
attackStart.TimelineEvent.fieldAction	`COMPLETED` `NOTPERFORMED` `INPROGRESS` `PAUSED` `ABANDON`	`completed` `not_performed` `in_progress` `paused` `abandoned`
attackStop.TimelineEvent.fieldAction	`COMPLETED` `NOTPERFORMED` `INPROGRESS` `PAUSED` `ABANDON`	`completed` `not_performed` `in_progress` `paused` `abandoned`

Content Library Queries¶

Since VECTR 9.0, the “GoldStandard” database reference has been deprecated, and will eventually get phased out. New queries have been added to specifically target Content Library data, formerly known as "GoldStandard". These queries are prefixed with “library” and omits the “db” parameter, but are otherwise equivalent as the non “library” query. If you are currently using a GraphQL query to pull data from “GoldStandard”, we recommend using the “library” equivalent as the usage of “GoldStandard” on a non “library” query will not be supported in a future VECTR version.

Here are a couple of example query definitions of a non “library” query and its equivalent “library” query:

Query	Library Query
`testCase` ( `db`:`String!` `id`:`String` ):`TestCase`	`libraryTestCase` ( `id`:`String` ):`TestCase`
`testCases` ( `db`:`String!` `filter`: `TestCaseFilter` `first`:`Int` `after`:`String` `orderBy`:`TestCaseSortOrder = {field: NAME, direction: ASC}` ):`TestCaseConnection`	`libraryTestCases` ( `filter`: `TestCaseFilter` `first`:`Int` `after`:`String` `orderBy`:`TestCaseSortOrder = {field: NAME, direction: ASC}` ):`TestCaseConnection`
`testcasesByIds` ( `db`:`String!` `id`:`[String]!` ):`TestCaseConnection`	`libraryTestcasesByIds` ( `id`:`[String]!` ):`TestCaseConnection`

New Types¶

DefenseToolProduct
AutomationArgument
TagType

New Fields¶

Type/Enum	Field
Database	`id`
DefensiveLayer	`template`
BlueTool	`active` `defenseToolProduct` `template`
TagTypeEnum	`DETECTION_RULE`
RedTool	`active` `toolVersion`
Tag	`tagTypeId` `sys`

New Inputs¶

Query	Input
bluetools	`filter`

New Queries and Mutations¶

Name	Description
`TestCaseMutation.updateTemplate`	Update for existing library testcases
`DefenseToolProduct.defenseToolProducts`	Query for all defense tool products
`TestCaseMutation.updateTemplate`	Query for defense tool products of the provided ids
`TagType.tagTypes`	Query for all tag types