AWS Security Hub
Since Camel 4.18
Only producer is supported
The AWS Security Hub component allows you to interact with AWS Security Hub to manage security findings.
AWS Security Hub provides a comprehensive view of your security state in AWS and helps you check your environment against security industry standards and best practices.
Prerequisites
You must have a valid Amazon Web Services developer account, and be signed up to use Amazon Security Hub. More information is available at Amazon Security Hub.
URI Format
aws-security-hub://label[?options]
You can append query options to the URI in the following format:
?options=value&option2=value&…
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
At the component level, you set general and shared configurations that are, then, inherited by the endpoints. It is the highest configuration level.
For example, a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre-configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
You can configure components using:
-
the Component DSL.
-
in a configuration file (
application.properties,*.yamlfiles, etc). -
directly in the Java code.
Configuring Endpoint Options
You usually spend more time setting up endpoints because they have many options. These options help you customize what you want the endpoint to do. The options are also categorized into whether the endpoint is used as a consumer (from), as a producer (to), or both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL and DataFormat DSL as a type safe way of configuring endpoints and data formats in Java.
A good practice when configuring options is to use Property Placeholders.
Property placeholders provide a few benefits:
-
They help prevent using hardcoded urls, port numbers, sensitive information, and other settings.
-
They allow externalizing the configuration from the code.
-
They help the code to become more flexible and reusable.
The following two sections list all the options, firstly for the component followed by the endpoint.
Component Options
The AWS Security Hub component supports 22 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
Component configuration. | SecurityHubConfiguration | ||
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean | |
Required The operation to perform. Enum values:
| batchImportFindings | SecurityHubOperations | |
Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option. | false | boolean | |
If we want to use a POJO request as body or not. | false | boolean | |
The region in which the Security Hub client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You’ll need to use the name Region.EU_WEST_1.id(). Enum values:
| String | ||
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | boolean | |
Autowired To use an existing configured AWS Security Hub client. | SecurityHubClient | ||
Used for enabling or disabling all consumer based health checks from this component. | true | boolean | |
Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true. | true | boolean | |
To define a proxy host when instantiating the Security Hub client. | String | ||
To define a proxy port when instantiating the Security Hub client. | Integer | ||
To define a proxy protocol when instantiating the Security Hub client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | String | ||
If using a profile credentials provider this parameter will set the profile name. | String | ||
Amazon AWS Secret Key. | String | ||
Amazon AWS Session Token used when the user needs to assume an IAM role. | String | ||
If we want to trust all certificates in case of overriding the endpoint. | false | boolean | |
Set whether the Security Hub client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | boolean | |
Set whether the Security Hub client should expect to load credentials through a profile credentials provider. | false | boolean | |
Set whether the Security Hub client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Security Hub. | false | boolean |
Endpoint Options
The AWS Security Hub endpoint is configured using URI syntax:
aws-security-hub:label
With the following path and query parameters:
Query Parameters (18 parameters)
| Name | Description | Default | Type |
|---|---|---|---|
Required The operation to perform. Enum values:
| batchImportFindings | SecurityHubOperations | |
Set the need for overriding the endpoint. This option needs to be used in combination with the uriEndpointOverride option. | false | boolean | |
If we want to use a POJO request as body or not. | false | boolean | |
The region in which the Security Hub client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example, ap-east-1) You’ll need to use the name Region.EU_WEST_1.id(). Enum values:
| String | ||
Set the overriding uri endpoint. This option needs to be used in combination with overrideEndpoint option. | String | ||
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean | |
Autowired To use an existing configured AWS Security Hub client. | SecurityHubClient | ||
To define a proxy host when instantiating the Security Hub client. | String | ||
To define a proxy port when instantiating the Security Hub client. | Integer | ||
To define a proxy protocol when instantiating the Security Hub client. Enum values:
| HTTPS | Protocol | |
Amazon AWS Access Key. | String | ||
If using a profile credentials provider this parameter will set the profile name. | String | ||
Amazon AWS Secret Key. | String | ||
Amazon AWS Session Token used when the user needs to assume an IAM role. | String | ||
If we want to trust all certificates in case of overriding the endpoint. | false | boolean | |
Set whether the Security Hub client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. | false | boolean | |
Set whether the Security Hub client should expect to load credentials through a profile credentials provider. | false | boolean | |
Set whether the Security Hub client should expect to use Session Credentials. This is useful in a situation in which the user needs to assume an IAM role for doing operations in Security Hub. | false | boolean |
Message Headers
The AWS Security Hub component supports 21 message header(s), which is/are listed below:
| Name | Description | Default | Type |
|---|---|---|---|
CamelAwsSecurityHubOperation (producer) Constant: | The operation we want to perform. | String | |
CamelAwsSecurityHubFindings (producer) Constant: | The list of findings to import. | List | |
CamelAwsSecurityHubFindingIdentifiers (producer) Constant: | The finding identifiers for batch update. | List | |
CamelAwsSecurityHubFilters (producer) Constant: | The filters to apply when retrieving findings. | AwsSecurityFindingFilters | |
CamelAwsSecurityHubNote (producer) Constant: | The note to add to findings during update. | NoteUpdate | |
CamelAwsSecurityHubSeverity (producer) Constant: | The severity to set on findings during update. | SeverityUpdate | |
CamelAwsSecurityHubWorkflow (producer) Constant: | The workflow status to set on findings. | WorkflowUpdate | |
CamelAwsSecurityHubVerificationState (producer) Constant: | The verification state to set on findings. | String | |
CamelAwsSecurityHubConfidence (producer) Constant: | The confidence level to set on findings. | Integer | |
CamelAwsSecurityHubCriticality (producer) Constant: | The criticality level to set on findings. | Integer | |
CamelAwsSecurityHubUserDefinedFields (producer) Constant: | User-defined fields to add to findings. | Map | |
CamelAwsSecurityHubRelatedFindings (producer) Constant: | Related findings to associate. | List | |
CamelAwsSecurityHubTypes (producer) Constant: | The types to assign to findings. | List | |
CamelAwsSecurityHubNextToken (getFindings listEnabledProductsForImport getFindingHistory) Constant: | The token for the next set of results. | String | |
CamelAwsSecurityHubMaxResults (getFindings) Constant: | The maximum number of results to return. | Integer | |
CamelAwsSecurityHubFailedCount (batchImportFindings) Constant: | The count of findings that failed to import. | Integer | |
CamelAwsSecurityHubSuccessCount (batchImportFindings) Constant: | The count of findings that were successfully imported. | Integer | |
CamelAwsSecurityHubUnprocessedFindings (batchUpdateFindings) Constant: | The list of findings that were not updated. | List | |
CamelAwsSecurityHubProcessedFindings (batchUpdateFindings) Constant: | The list of findings that were updated successfully. | List | |
CamelAwsSecurityHubFindingId (getFindingHistory) Constant: | The finding ID to get history for. | String | |
CamelAwsSecurityHubProductArn (getFindingHistory) Constant: | The product ARN for the finding. | String |
Usage
Static credentials, Default Credential Provider and Profile Credentials Provider
You have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
The order of evaluation for Default Credentials Provider is the following:
-
Java system properties -
aws.accessKeyIdandaws.secretKey. -
Environment variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. -
Web Identity Token from AWS STS.
-
The shared credentials and config files.
-
Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIis set. -
Amazon EC2 Instance profile credentials.
You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
Only one of static, default and profile credentials could be used at the same time.
For more information about this you can look at AWS credentials documentation
AWS Security Hub Producer operations
Camel-AWS Security Hub component provides the following operation on the producer side:
-
batchImportFindings
-
getFindings
-
batchUpdateFindings
-
getFindingHistory
-
describeHub
-
listEnabledProductsForImport
BatchImportFindings
Import security findings into Security Hub. This is the primary way to send findings from custom integrations.
from("direct:importFindings")
.process(exchange -> {
AwsSecurityFinding finding = AwsSecurityFinding.builder()
.schemaVersion("2018-10-08")
.id("my-finding-id")
.productArn("arn:aws:securityhub:us-east-1:123456789012:product/123456789012/default")
.generatorId("my-generator")
.awsAccountId("123456789012")
.types("Software and Configuration Checks/Vulnerabilities/CVE")
.createdAt("2024-01-15T00:00:00.000Z")
.updatedAt("2024-01-15T00:00:00.000Z")
.severity(Severity.builder().label(SeverityLabel.HIGH).build())
.title("Critical vulnerability found")
.description("A critical vulnerability was detected")
.resources(Resource.builder()
.type("AwsEc2Instance")
.id("arn:aws:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0")
.build())
.build();
exchange.getIn().setBody(List.of(finding));
})
.to("aws-security-hub://findings?operation=batchImportFindings")
.to("mock:result"); GetFindings
Retrieve security findings from Security Hub with optional filtering.
from("direct:getFindings")
.process(exchange -> {
AwsSecurityFindingFilters filters = AwsSecurityFindingFilters.builder()
.severityLabel(StringFilter.builder()
.comparison(StringFilterComparison.EQUALS)
.value("CRITICAL")
.build())
.build();
exchange.getIn().setHeader(SecurityHubConstants.FILTERS, filters);
exchange.getIn().setHeader(SecurityHubConstants.MAX_RESULTS, 10);
})
.to("aws-security-hub://findings?operation=getFindings")
.to("mock:result"); BatchUpdateFindings
Update security findings with notes, severity changes, workflow status, etc.
from("direct:updateFindings")
.process(exchange -> {
List<AwsSecurityFindingIdentifier> identifiers = List.of(
AwsSecurityFindingIdentifier.builder()
.id("my-finding-id")
.productArn("arn:aws:securityhub:us-east-1:123456789012:product/123456789012/default")
.build()
);
exchange.getIn().setHeader(SecurityHubConstants.FINDING_IDENTIFIERS, identifiers);
NoteUpdate note = NoteUpdate.builder()
.text("Reviewed and confirmed as false positive")
.updatedBy("security-team")
.build();
exchange.getIn().setHeader(SecurityHubConstants.NOTE, note);
WorkflowUpdate workflow = WorkflowUpdate.builder()
.status(WorkflowStatus.RESOLVED)
.build();
exchange.getIn().setHeader(SecurityHubConstants.WORKFLOW, workflow);
})
.to("aws-security-hub://findings?operation=batchUpdateFindings")
.to("mock:result"); OCSF Integration
AWS Security Hub uses the Open Cybersecurity Schema Framework (OCSF) for findings. You can use the Camel OCSF DataFormat to work with security events in a vendor-neutral format, then convert them for import into Security Hub.
from("direct:ocsfToSecurityHub")
.unmarshal().ocsf(DetectionFinding.class)
.process(exchange -> {
DetectionFinding ocsf = exchange.getIn().getBody(DetectionFinding.class);
// Convert OCSF finding to AWS Security Finding format
AwsSecurityFinding finding = convertToAwsFinding(ocsf);
exchange.getIn().setBody(List.of(finding));
})
.to("aws-security-hub://findings?operation=batchImportFindings"); Dependencies
Maven users will need to add the following dependency to their pom.xml.
pom.xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-aws-security-hub</artifactId>
<version>${camel-version}</version>
</dependency> where ${camel-version} must be replaced by the actual version of Camel.