Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Actor
Represents an actor used during penetration testing. An actor defines a user or entity that interacts with the target application, including authentication credentials and target URIs.
- Agent
Space Represents an agent space, which is a dedicated workspace for securing a specific application. An agent space contains the configuration, resources, and settings needed for security testing.
- Agent
Space Summary Contains summary information about an agent space.
- Application
Summary Contains summary information about an application.
- Artifact
Represents an artifact that provides context for security testing, such as documentation, diagrams, or configuration files.
- Artifact
Metadata Item Contains metadata about an artifact.
- Artifact
Summary Contains summary information about an artifact.
- Assets
The collection of assets used in a pentest configuration, including endpoints, actors, documents, source code repositories, and integrated repositories.
- Authentication
The authentication configuration for an actor, specifying the provider type and credentials.
- AwsResources
The AWS resources associated with an agent space, including VPCs, log groups, S3 buckets, secrets, Lambda functions, and IAM roles.
- Batch
Create Security Requirement Result Contains information about a successfully created security requirement.
- Batch
GetSecurity Requirement Result Contains information about a successfully retrieved security requirement.
- Batch
Security Requirement Error Contains information about an error that occurred for a specific security requirement during a batch operation.
- Bitbucket
Integration Input The configuration for creating a Bitbucket integration.
- Bitbucket
Repository Metadata Metadata for an integrated Bitbucket repository.
- Bitbucket
Repository Resource A Bitbucket repository integrated as a resource.
- Bitbucket
Resource Capabilities Capabilities for an integrated Bitbucket repository.
- Category
Represents a category assigned to a security testing task.
- Cloud
Watch Log The Amazon CloudWatch Logs configuration for pentest job logging.
- Code
Location Represents a location in source code associated with a security finding.
- Code
Remediation Task Represents a code remediation task that was initiated to fix a security finding.
- Code
Remediation Task Details Contains details about a code remediation task, including links to the code diff and pull request.
- Code
Review Represents a code review configuration that defines the parameters for automated security-focused code analysis, including target assets and logging configuration.
- Code
Review Job Represents a code review job, which is an execution instance of a code review. A code review job progresses through preflight, static analysis, and finalizing steps.
- Code
Review JobSummary Contains summary information about a code review job.
- Code
Review JobTask Represents an individual security test task within a code review job. Each task targets a specific risk type and executes independently.
- Code
Review JobTask Summary Contains summary information about a code review job task.
- Code
Review Settings The code review settings for an agent space, controlling which types of scanning are enabled.
- Code
Review Summary Contains summary information about a code review.
- Confluence
Document Metadata Metadata for an integrated Confluence document.
- Confluence
Document Resource A Confluence document (page) integrated as a resource.
- Confluence
Integration Input The configuration for creating a Confluence integration.
- Confluence
Resource Capabilities Capabilities for an integrated Confluence space.
- Create
Security Requirement Entry Contains the details for a security requirement to create within a pack.
- Custom
Header A custom HTTP header to include in network traffic during penetration testing.
- Delete
Code Review Failure Contains information about a code review that failed to delete.
- Delete
Pentest Failure Contains information about a pentest that failed to delete.
- Delete
Threat Model Failure Contains information about a threat model that failed to delete.
- Discovered
Endpoint Represents an endpoint discovered during a pentest job.
- DnsVerification
Contains DNS verification details for a target domain, including the DNS record to create for domain ownership verification.
- Document
Info Represents a document that provides context for security testing.
- Endpoint
Represents a target endpoint for penetration testing.
- Error
Information Contains error information for a pentest job that encountered an error.
- Execution
Context Contains contextual information about the execution of a pentest job, such as errors, warnings, or informational messages.
- Finding
Represents a security finding discovered during a pentest job. A finding contains details about a vulnerability, including its risk level, confidence, and remediation status.
- Finding
Summary Contains summary information about a security finding.
- GitHub
Integration Input The input required to create a GitHub integration, including the OAuth authorization code and CSRF state.
- GitHub
Repository Metadata Contains metadata about a GitHub repository that is integrated with the service.
- GitHub
Repository Resource Represents a GitHub repository resource used in an integration.
- GitHub
Resource Capabilities The capabilities enabled for a GitHub resource integration.
- GitLab
Integration Input The configuration for creating a GitLab integration.
- GitLab
Repository Metadata Metadata for an integrated GitLab repository.
- GitLab
Repository Resource A GitLab repository integrated as a resource.
- GitLab
Resource Capabilities Capabilities for an integrated GitLab repository.
- Http
Verification Contains HTTP route verification details for a target domain, including the route path and token to serve for domain ownership verification.
- IdCConfiguration
The IAM Identity Center configuration for an application.
- Integrated
Document A reference to a document in a third-party provider, such as a Confluence page linked via an integration.
- Integrated
Repository Represents a code repository that is integrated with the service through a third-party provider.
- Integrated
Resource Input Item Represents an input item for updating integrated resources, including the resource and its capabilities.
- Integrated
Resource Summary Contains summary information about an integrated resource.
- Integration
Summary Contains summary information about an integration.
- List
Security Requirement Pack Filter Filter criteria for listing security requirement packs.
- LogLocation
The log location for a task, specifying where task execution logs are stored.
- Membership
Summary Contains summary information about a membership.
- Network
Traffic Config The network traffic configuration for a pentest, including custom headers and traffic rules.
- Network
Traffic Rule A rule that controls network traffic during penetration testing by allowing or denying traffic to specific URL patterns.
- Pentest
Represents a pentest configuration that defines the parameters for security testing, including target assets, risk type exclusions, and infrastructure settings.
- Pentest
Job Represents a pentest job, which is an execution instance of a pentest. A pentest job progresses through preflight, static analysis, pentest, and finalizing steps.
- Pentest
JobSummary Contains summary information about a pentest job.
- Pentest
Summary Contains summary information about a pentest.
- Private
Connection Summary Summarizes a private connection.
- Report
Destination Destination for publishing scan reports to an integrated document provider.
- Security
Requirement Artifact A document used as source material for importing security requirements.
- Security
Requirement Pack Summary Contains summary information about a security requirement pack.
- Security
Requirement Summary Contains summary information about a security requirement.
- Self
Managed Input The configuration for a self-managed private connection.
- Service
Managed Input The configuration for a service-managed private connection.
- Source
Code Repository Represents a source code repository used for security analysis during a pentest.
- Step
Represents a step in the pentest job execution pipeline. Steps include preflight, static analysis, pentest, and finalizing.
- Target
Domain Represents a target domain registered for penetration testing. A target domain must be verified through DNS TXT or HTTP route verification before it can be used in pentests.
- Target
Domain Summary Contains summary information about a target domain.
- Task
Represents an individual security test task within a pentest job. Each task targets a specific risk type or endpoint and executes independently.
- Task
Summary Contains summary information about a task.
- Threat
Represents a threat identified during threat modeling.
- Threat
Anchor Shape DFD element that a threat is anchored to.
- Threat
Evidence Shape Source code file supporting a threat.
- Threat
Model Represents a threat model configuration that defines the parameters for automated threat analysis, including target assets and logging configuration.
- Threat
Model Job Represents a threat model job, which is an execution instance of a threat model.
- Threat
Model JobSummary Contains summary information about a threat model job.
- Threat
Model JobTask Represents an individual task within a threat model job.
- Threat
Model JobTask Summary Contains summary information about a threat model job task.
- Threat
Model Summary Contains summary information about a threat model.
- Threat
Summary Contains summary information about a threat.
- Update
Security Requirement Entry Contains the details for updating an existing security requirement within a pack. The name is an immutable identifier used to locate the requirement and cannot be modified.
- User
Config The configuration for a user membership, including the role assigned to the user within the agent space.
- User
Metadata Contains metadata about a user member, including the username and email address.
- Validation
Exception Field Describes one specific validation failure for an input member.
- Verification
Details Contains the verification details for a target domain, including the verification method and provider-specific details.
- Verification
Script Contains metadata for a verification script that can be used to reproduce a security finding.
- Verification
Script EnvVar Represents an environment variable required to run a verification script.
- VpcConfig
The VPC configuration for a pentest, specifying the VPC, security groups, and subnets to use during testing.
Enums§
- Access
Type - When writing a match expression against
AccessType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Artifact
Type - When writing a match expression against
ArtifactType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Authentication
Provider Type - When writing a match expression against
AuthenticationProviderType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Clean
UpStrategy - When writing a match expression against
CleanUpStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Code
Remediation Strategy - When writing a match expression against
CodeRemediationStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Code
Remediation Task Status - When writing a match expression against
CodeRemediationTaskStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Confidence
Level - When writing a match expression against
ConfidenceLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Context
Type - When writing a match expression against
ContextType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Diff
Source Source of the diff for a differential code scan.
- DnsRecord
Type - When writing a match expression against
DnsRecordType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Domain
Verification Method - When writing a match expression against
DomainVerificationMethod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Error
Code - When writing a match expression against
ErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Finding
Status - When writing a match expression against
FindingStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - GitLab
Token Type - When writing a match expression against
GitLabTokenType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Import
Source The source from which to import security requirements. Currently supports document uploads.
- Integrated
Resource Represents an integrated resource from a third-party provider. This is a union type that contains provider-specific resource information.
- Integrated
Resource Metadata Contains metadata about an integrated resource. This is a union type that contains provider-specific metadata.
- Integration
Filter A filter for listing integrations. This is a union type where you can filter by provider or provider type.
- IpAddress
Type - When writing a match expression against
IpAddressType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - JobStatus
- When writing a match expression against
JobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - LogType
- When writing a match expression against
LogType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Management
Type - When writing a match expression against
ManagementType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Member
Metadata Contains metadata about a member. This is a union type that contains member-type-specific metadata.
- Membership
Config The configuration for a membership. This is a union type that contains member-type-specific configuration.
- Membership
Type - When writing a match expression against
MembershipType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Membership
Type Filter - When writing a match expression against
MembershipTypeFilter, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Traffic Rule Effect - When writing a match expression against
NetworkTrafficRuleEffect, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Traffic Rule Type - When writing a match expression against
NetworkTrafficRuleType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Private
Connection Mode The configuration for a private connection. Specify either a service-managed or a self-managed mode.
- Private
Connection Status - When writing a match expression against
PrivateConnectionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Private
Connection Type - When writing a match expression against
PrivateConnectionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Provider
- When writing a match expression against
Provider, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Provider
Input The provider-specific input for creating an integration. This is a union type that contains provider-specific configuration.
- Provider
Resource Capabilities The capabilities for an integrated resource from a third-party provider. This is a union type that contains provider-specific capabilities.
- Provider
Type - When writing a match expression against
ProviderType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Resource
Config DnsResolution - When writing a match expression against
ResourceConfigDnsResolution, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Resource
Type - When writing a match expression against
ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Risk
Level - When writing a match expression against
RiskLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Risk
Type - When writing a match expression against
RiskType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Security
Requirement Artifact Format - When writing a match expression against
SecurityRequirementArtifactFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Security
Requirement Pack Import Status - When writing a match expression against
SecurityRequirementPackImportStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Security
Requirement Pack Status - When writing a match expression against
SecurityRequirementPackStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Skill
Type - When writing a match expression against
SkillType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Step
Name - When writing a match expression against
StepName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Step
Status - When writing a match expression against
StepStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Stride
Category - When writing a match expression against
StrideCategory, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Target
Domain Status - When writing a match expression against
TargetDomainStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Task
Execution Status - When writing a match expression against
TaskExecutionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Threat
Actor - When writing a match expression against
ThreatActor, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Threat
Severity - When writing a match expression against
ThreatSeverity, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Threat
Status - When writing a match expression against
ThreatStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - User
Role - When writing a match expression against
UserRole, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Validation
Mode - When writing a match expression against
ValidationMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Validation
Status - When writing a match expression against
ValidationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.