Skip to main content

SecurityGateExecution

No description

type SecurityGateExecution implements BaseFields {
  asset: Asset!
  branch: Branch
  configurationOwnerType: String
  createdAt: ISO8601DateTime!
  evaluatedRules: JSON
  executionDate: ISO8601DateTime
  failingPrFindings: [PullRequestScanFinding!]!
  failingPreExistingVulnerabilities(
    pagination: BasePaginationInput
  ): SecurityGateFailingVulnerabilityCollection!
  failingVulnerabilities(
    pagination: BasePaginationInput
  ): SecurityGateFailingVulnerabilityCollection!
  id: ID
  issuesUrl: String
  lastScans: ControlSyncStatusCollection
  prEvaluationScope: SecurityGatePrEvaluationScopeEnum
  reason: SecurityGateExecutionReason
  scanRunId: ID
  securityGateConfiguration: SecurityGateConfiguration
  source: SecurityGateRuleSourceEnum
  status: SecurityGateExecutionResultEnum!
  triggerScan: ControlSyncStatus
  triggeredBy: String!
  updatedAt: ISO8601DateTime!
}

Fields​

SecurityGateExecution.asset ● Asset! non-null object​

SecurityGateExecution.branch ● Branch object​

The branch this run evaluated. Null for a legacy asset, which is gated as a whole.

SecurityGateExecution.configurationOwnerType ● String scalar​

Whether the evaluated configuration was the Asset's or the company Scope's, as it was at execution time

SecurityGateExecution.createdAt ● ISO8601DateTime! non-null scalar​

The date when record was created

SecurityGateExecution.evaluatedRules ● JSON scalar​

The severity limits as they were when this verdict was issued. Editing the configuration afterwards does not change them.

SecurityGateExecution.executionDate ● ISO8601DateTime scalar​

SecurityGateExecution.failingPrFindings ● [PullRequestScanFinding!]! non-null object​

The run-scoped pull request evidence that caused this verdict. Empty for an inventory-triggered execution, whose evidence is failingVulnerabilities, and empty once the 21-day evidence retention has run.

SecurityGateExecution.failingPreExistingVulnerabilities ● SecurityGateFailingVulnerabilityCollection! non-null object​

Pending issues already open on the pull request's target branch that counted toward this verdict. Always empty unless prEvaluationScope is DELTA_AND_PRE_EXISTING.

SecurityGateExecution.failingPreExistingVulnerabilities.pagination ● BasePaginationInput input​

SecurityGateExecution.failingVulnerabilities ● SecurityGateFailingVulnerabilityCollection! non-null object​

Vulnerabilities that caused the security gate to fail

SecurityGateExecution.failingVulnerabilities.pagination ● BasePaginationInput input​

SecurityGateExecution.id ● ID scalar​

The ID scalar type represents a unique identifier

SecurityGateExecution.issuesUrl ● String scalar​

SecurityGateExecution.lastScans ● ControlSyncStatusCollection object​

Last scan per integration for the execution asset

SecurityGateExecution.prEvaluationScope ● SecurityGatePrEvaluationScopeEnum enum​

The scope in effect when this verdict was produced. Null for inventory-triggered executions.

SecurityGateExecution.reason ● SecurityGateExecutionReason object​

SecurityGateExecution.scanRunId ● ID scalar​

The pull request scan run whose evidence produced this verdict. Null for inventory-triggered executions.

SecurityGateExecution.securityGateConfiguration ● SecurityGateConfiguration object​

SecurityGateExecution.source ● SecurityGateRuleSourceEnum enum​

SecurityGateExecution.status ● SecurityGateExecutionResultEnum! non-null enum​

SecurityGateExecution.triggerScan ● ControlSyncStatus object​

The scan sync whose completion triggered this execution (null for manual runs)

SecurityGateExecution.triggeredBy ● String! non-null scalar​

SecurityGateExecution.updatedAt ● ISO8601DateTime! non-null scalar​

The date when record was updated

Interfaces​

BaseFields interface​

Returned By​

securityGateExecution query ● securityGateRun query

Member Of​

ControlSyncStatus object ● IntegrationDetails object ● PullRequestScanRun object ● SecurityGateExecutionCollection object

Contribute to the Docs

Found something outdated or missing? Help us improve the documentation with a quick suggestion or edit.

How to contribute

Resources

By exploring our content, you'll find resources that will enhance your understanding of the importance of a Security Application Program.

Conviso Blog: Explore our blog, which offers a collection of articles and posts covering a wide range of AppSec topics. The content on the blog is primarily in English.

Conviso's YouTube Channel: Access a wealth of informative videos covering various topics related to AppSec. Please note that the content is primarily in Portuguese.