WithSecure Elements Integration
Serverless Observability Serverless Security Stack
| Version | 0.1.0 (View all) |
| Subscription level What's this? |
Basic |
| Developed by What's this? |
Community |
| Ingestion method(s) | API |
To use beta 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.
- 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 | Kibana version(s) |
|---|---|---|
| 0.1.0 | Enhancement (View pull request) Initial release. |
— |