WithSecure Elements Integration
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Observability
Preview
Preview
Serverless Security
Preview
Preview
Stack
Preview
9.0+
Preview since 9.0
| Version | 0.5.0 Availability Preview This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. (View all) |
| Managed integration release status | GA |
| Subscription level What's this? |
Basic |
| Developed by What's this? |
Community |
| Ingestion method(s) | API |
| Minimum Kibana version(s) | 9.0.5 8.19.2 |
You can use this integration as an Elastic Managed integration on Elastic Cloud Hosted deployments running this version or later.
To use pre-release integrations, go to the Integrations page in Kibana, scroll down, and toggle on the Display beta integrations option.
This integration allows you to collect data from the WithSecure Elements API, including incidents (Broad Context Detections - BCDs) and security events.
Elastic Managed integrations are only supported on Elastic Cloud Serverless and Elastic Cloud Hosted deployments. An Elastic Managed integration lets you ingest data from a cloud source while avoiding the orchestration, management, and maintenance associated with standard ingest infrastructure. Elastic runs the collector for you, so you can focus on your data instead of the infrastructure that collects it.
For more information, refer to Elastic Managed integrations and the Elastic Managed integrations FAQ.
- WithSecure Elements Client ID and Client Secret
- Organization ID
- Access to WithSecure Elements API
This integration uses a single input configuration for all data streams. You only need to configure the API credentials once:
- URL: WithSecure Elements API URL (default: https://api.connect.withsecure.com)
- Client ID: Client ID for OAuth2 authentication
- Client Secret: Client Secret for OAuth2 authentication
- Organization ID: Organization identifier
You can enable/disable each data stream individually. Each data stream has its own collection interval:
Collects Broad Context Detections (BCDs) from WithSecure Elements API.
- Interval: Collection interval (default: 5m)
- API Endpoint:
GET /incidents/v1/incidents - Max items per request: 50
Collects security events from WithSecure Elements API (EPP and EDR engines).
- Interval: Collection interval (default: 5m)
- API Endpoint:
POST /security-events/v1/security-events - Max items per request: 200
- Engines: EPP (Endpoint Protection) and EDR (Detection and Response)
Collects detections for specific incidents from WithSecure Elements API.
- Incident ID: Specific Incident ID to collect detections for
- Interval: Collection interval (default: 5m)
- Note: Requires a valid incident ID. Enable this data stream only if you need detections for specific incidents.
- Security incident information
- Status, severity, risk level
- Categories and sources
- Creation and update timestamps
- Comments and assignments
- Real-time security events from EPP and EDR
- Actions taken (blocked, quarantined, deleted, etc.)
- Device and user information
- Engine-specific details (DeepGuard, Application Control, DataGuard, etc.)
- Severity levels (critical, warning, info)
- Detections specific to each incident
- Detailed threat detection information
- Data on files, users, and devices involved
- Network and behavioral information
Data is mapped to the Elastic Common Schema (ECS) with the following fields:
event.category: Event categoryevent.type: Event typeevent.severity: Severity levelevent.action: Action takenevent.provider: Provider (withsecure_elements)event.id: Unique event identifierevent.created: Event creation timestamp@timestamp: Event timestamp
The integration uses OAuth2 client credentials flow for authentication:
- Token URL:
{API_URL}/as/token.oauth2 - Grant Type:
client_credentials - Scope:
connect.api.read
For any questions or issues, please refer to the WithSecure Elements documentation or contact support.
Changelog
| Version | Details | Minimum Kibana version |
|---|---|---|
| 0.5.0 | Enhancement (View pull request) Update Elastic Managed integration documentation to the current wording and docs links. |
9.0.5 8.19.2 |
| 0.4.0 | Enhancement (View pull request) Add tags to ingest pipeline processors and add preserve_original_event to pipeline-level on_failure handlers.Bug fix (View pull request) Append to error.message in the pipeline-level on_failure handlers instead of overwriting messages recorded by processor-level handlers. |
9.0.5 8.19.2 |
| 0.3.1 | Enhancement (View pull request) Set agentless deployment mode release field to ga. |
9.0.5 8.19.2 |
| 0.3.0 | Enhancement (View pull request) Enable Agentless deployment. |
9.0.5 8.19.2 |
| 0.2.0 | Enhancement (View pull request) Enable request trace log removal. |
9.0.0 8.18.0 |
| 0.1.0 | Enhancement (View pull request) Initial release. |
9.0.0 8.18.0 |