Connect this data source on your own, using the Hunters platform.
TL;DR
Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method |
|---|---|---|---|---|---|---|---|
Very Good Security Events | ✅ | ✅ | very_good_security_events | NDJSON | Webhook/S3 |
Overview
Very Good Security is a data security platform that focuses on protecting sensitive data by providing tokenization and encryption services. It helps organizations securely store, process, and transmit data without ever exposing the sensitive information itself. VGS acts as a proxy between systems, replacing sensitive data with secure tokens, ensuring compliance with industry regulations like PCI-DSS, HIPAA, and GDPR. By abstracting the data security layer, VGS simplifies security management, reduces risk, and allows businesses to maintain full control over their data without the complexity of managing sensitive information directly.
Supported data types
Very Good Security Events
Table name: very_good_security_events
The event logs generated by VGS offer comprehensive records of all data transactions, security events, and system interactions within the platform. These logs are essential for monitoring data access and flows, detecting potential security incidents, and ensuring compliance with data protection regulations. By meticulously logging every event associated with sensitive data, VGS event logs help organizations maintain a high level of security and operational integrity, providing them with the insights needed to manage risk effectively and demonstrate compliance with industry standards and regulatory requirements.
Learn more here.
Send data to Hunters
Hunters supports the ingestion of Very Good Security Events using one of the following methods:
Webhoook
S3
Connect using webhook
Set up the Very Good Security webhook following this guide.
Acquire a webhook URL from Very Good Security for the integration.
Contact support to establish the connection.
Connect using S3
Route your Very Good Security logs to an AWS S3 bucket.
Once the export is completed and the logs are collected to S3, follow the steps in this section.
Expected format
Logs are expected in NDJSON format.
{"description": "Proxy or Vault API reveal failed", "details": {"environment": "sandbox", "storage": "volatile"}, "event": "alias.reveal_failed", "fingerprint": "abcdefce93fd257ec17daf62587d9fd8beb12345", "grouping": "exp_repeat", "id": "abcd-bab3-4650-afe3-3da746b50ac0", "integration_id": "12345ofH2sCj7qhFFDofU", "occurrence": 1, "org_id": "ABCD1234TbuzYKaGotNN", "producer": {"application_name": "http-proxy", "application_protocol": "http"}, "scope": "vault", "summary": "1 failed reveals occured within vault abcdses5f in sandbox", "tenant": "abcdbses5f", "timestamp": "2023-07-11T10:58:41.685Z"}