{
  "schemaVersion": "1.2.0",
  "schema": "https://hivesilo.com/evidence/company-fact-sheet.schema.json",
  "slug": "elastic",
  "product": "Elastic",
  "url": "https://hivesilo.com/integrations/elastic",
  "title": "Elastic Integration: Audit Events by Bulk API in ECS | HiveSilo",
  "description": "Elastic integration with HiveSilo: tenant audit and security events written to your Elasticsearch deployment through the Bulk API, with an API key you create and control.",
  "reviewed": "2026-11-11",
  "connectionStatus": "available",
  "image": {
    "width": 1800,
    "height": 1195,
    "group": "security",
    "alt": "Illustrative enterprise office at dusk for the Elastic integration workflow",
    "heroVariants": [
      {
        "path": "/img/integrations/elastic-integration-security-480.854e22807114.webp",
        "width": 480,
        "height": 319,
        "bytes": 21216
      },
      {
        "path": "/img/integrations/elastic-integration-security-768.3a4946822424.webp",
        "width": 768,
        "height": 510,
        "bytes": 47770
      },
      {
        "path": "/img/integrations/elastic-integration-security-1200.742eae743649.webp",
        "width": 1200,
        "height": 797,
        "bytes": 98032
      },
      {
        "path": "/img/integrations/elastic-integration-security-1800.bc95e30e4f11.webp",
        "width": 1800,
        "height": 1195,
        "bytes": 169500
      }
    ],
    "socialImage": {
      "path": "/og/elastic-integration-intelligence.0a49cb479877.png",
      "width": 1200,
      "height": 630,
      "bytes": 768706
    },
    "retiredSocialImages": [],
    "sourceSha256": "40f59dc928a0",
    "source": "AI-generated illustrative scene; not a vendor or customer facility",
    "illustrative": true
  },
  "content": {
    "inventoryId": "P719",
    "slug": "elastic",
    "product": "Elastic",
    "shortName": "Elastic",
    "niche": "keys-siem",
    "connectionStatus": "available",
    "reviewed": "2026-11-11",
    "contentVersion": "1.2.0",
    "title": "Elastic Integration: Audit Events by Bulk API in ECS | HiveSilo",
    "description": "Elastic integration with HiveSilo: tenant audit and security events written to your Elasticsearch deployment through the Bulk API, with an API key you create and control.",
    "primaryKeyword": "Elastic integration",
    "secondaryKeywords": [
      "Elasticsearch bulk API audit logs",
      "Elastic Security custom log ingestion",
      "Elastic Common Schema audit events",
      "HiveSilo Elastic"
    ],
    "sources": [
      {
        "id": "P719-D01",
        "title": "Elasticsearch API: Bulk index or delete documents",
        "url": "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk",
        "supports": "POST /_bulk and POST /{index}/_bulk perform multiple actions in one request with a newline delimited JSON (NDJSON) body whose final line ends with a newline; the create action needs the create_doc, create, index or write index privilege; data streams support only the create action; there is no \"correct\" number of actions per request.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D02",
        "title": "Elasticsearch API documentation: Authentication",
        "url": "https://www.elastic.co/docs/api/doc/elasticsearch/authentication",
        "supports": "The API accepts bearer, basic and API key authentication; an API key is sent as \"Authorization: ApiKey\" with the encoded value, and keys come from the /_security/api_key APIs.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D03",
        "title": "Elasticsearch API: Create an API key",
        "url": "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-api-key",
        "supports": "POST /_security/api_key creates an API key; by default API keys never expire and an expiration can be set at creation; the call requires the manage_own_api_key cluster privilege.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D04",
        "title": "Elastic Docs: Elasticsearch API keys",
        "url": "https://www.elastic.co/docs/deploy-manage/api-keys/elasticsearch-api-keys",
        "supports": "API keys are managed in Kibana; using them there needs the manage_security, manage_api_key or manage_own_api_key cluster privilege, and deleting keys needs manage_api_key or manage_own_api_key; a personal key created from the Connection details panel has a default expiration of 90 days.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D05",
        "title": "Elasticsearch Reference: Networking settings",
        "url": "https://www.elastic.co/docs/reference/elasticsearch/configuration-reference/networking-settings",
        "supports": "http.max_content_length is the maximum size of an HTTP request body and defaults to 100mb.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D06",
        "title": "Elastic Common Schema (ECS) reference",
        "url": "https://www.elastic.co/docs/reference/ecs",
        "supports": "ECS is an open source specification that defines a common set of fields for storing event data, such as logs and metrics, in Elasticsearch.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D07",
        "title": "Elastic Common Schema: Event fields",
        "url": "https://www.elastic.co/docs/reference/ecs/ecs-event",
        "supports": "Defines the event field set, including event.action (the action captured by the event) and event.outcome (whether the event represents a success or a failure).",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D08",
        "title": "Elastic Common Schema: ECS categorization fields",
        "url": "https://www.elastic.co/docs/reference/ecs/ecs-category-field-values-reference",
        "supports": "ECS defines four categorization fields: event.kind, event.category, event.type and event.outcome. Events that match no published value should leave the fields empty.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D09",
        "title": "Elastic Common Schema: Custom fields",
        "url": "https://www.elastic.co/docs/reference/ecs/ecs-custom-fields-in-ecs",
        "supports": "Custom fields are allowed alongside ECS; nesting custom fields under a proper name, such as a company name, is described as a relatively safe approach.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D10",
        "title": "Elastic Security ECS field reference",
        "url": "https://www.elastic.co/docs/reference/security/fields-and-object-schemas/siem-field-reference",
        "supports": "Elastic Security requires event data to be normalized to ECS; all data must contain @timestamp, ecs.version, event.kind, event.category and event.type.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D11",
        "title": "Elastic Docs: Publish an integration via Pull Request",
        "url": "https://www.elastic.co/docs/extend/integrations/_publish_an_integration",
        "supports": "A published Elastic integration is a package added to the integrations repository by pull request and released to the package registry. HiveSilo does not claim an Elastic integration package.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D12",
        "title": "Elastic Docs: Elasticsearch ingest pipelines",
        "url": "https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines",
        "supports": "Ingest pipelines perform transformations on data before indexing through processors that run sequentially; managing them needs the manage_pipeline cluster privilege; Elastic recommends testing a pipeline with sample documents in Kibana or with the simulate pipeline API (POST _ingest/pipeline/_simulate); index.default_pipeline sets a default pipeline.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D13",
        "title": "Elastic Docs: Data streams in Elasticsearch",
        "url": "https://www.elastic.co/docs/manage-data/data-store/data-streams",
        "supports": "A data stream is a single named resource over backing indices optimized for append-only time series data such as logs and events; it requires a matching index template, and every document must contain a @timestamp field.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D14",
        "title": "Elastic Docs: Data stream lifecycle in Elasticsearch",
        "url": "https://www.elastic.co/docs/manage-data/lifecycle/data-stream",
        "supports": "Data stream lifecycle manages retention: data is kept at least for the retention time defined and data older than the retention period is deleted automatically later; retention can be configured on the data stream level or on a global level.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D15",
        "title": "Elastic Docs: Detections and alerts",
        "url": "https://www.elastic.co/docs/solutions/security/detect-and-alert",
        "supports": "Elastic Security's detection engine evaluates data against detection rules and generates alerts when rule criteria are met; the suggested lifecycle includes validating rule logic against historical data before enabling.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P719-D16",
        "title": "Elasticsearch Reference: Elasticsearch privileges",
        "url": "https://www.elastic.co/docs/reference/elasticsearch/security-privileges",
        "supports": "The create_doc index privilege allows indexing documents and does not grant permission to update or overwrite existing documents; the read index privilege gives read-only access to actions such as search and get.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "HSF1",
        "title": "HiveSilo capability overview",
        "url": "https://hivesilo.com/evidence/features.md",
        "supports": "Published HiveSilo capabilities relied on here: AI Governance & Control, AI firewall, bot defense and site protection, business insights and oversight, and client-controlled privacy and verification; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope.",
        "reviewed": "2026-11-11"
      }
    ],
    "hero": {
      "h1": "Elastic. HiveSilo audit events as documents in your own cluster.",
      "lede": "Elastic is where your team searches and investigates. HiveSilo writes its own audit and security events for your tenant to your Elasticsearch deployment through the Bulk API, with an API key you create.",
      "imageLines": [
        "Your cluster, your index.",
        "A vendor audit trail in it."
      ]
    },
    "problem": {
      "heading": "Your evidence is in Elasticsearch. Is your vendor's?",
      "summary": "Elastic can search and detect on the documents it stores. A vendor's administrative history is not among them until it is indexed.",
      "question": "What makes a vendor audit feed usable in Elastic?",
      "paragraphs": [
        "Teams on Elastic build detections, dashboards and saved searches over their indices and data streams. A vendor log that stays in a vendor console cannot be queried with the rest, and it follows a retention policy the team did not set.",
        "Elastic already provides the indexing, the security model and the schema. HiveSilo supplies the events: administrative and access actions in your HiveSilo tenant, data-rights requests, and traffic-protection alerts. They are written as documents to the index or data stream you name, on the deployment address you provide, and your own roles and lifecycle settings apply from there."
      ]
    },
    "value": {
      "heading": "Search HiveSilo activity with the queries you already have.",
      "summary": "HiveSilo does not add a console for your analysts. It writes tenant audit and security events to Elasticsearch, so Kibana and Elastic Security can read them like any other source.",
      "decisions": [
        {
          "title": "Who acted and how.",
          "body": "Query HiveSilo administrative and access actions beside events from your other systems."
        },
        {
          "title": "Where it is stored.",
          "body": "Choose the index or data stream, and the lifecycle that applies to it."
        },
        {
          "title": "What the key can do.",
          "body": "Limit the API key to writing documents to that one target."
        }
      ],
      "capabilities": [
        {
          "heading": "Documents through the Bulk API.",
          "body": "HiveSilo sends events in the newline delimited JSON format the Bulk API documents, to POST /_bulk or POST /{index}/_bulk on your deployment. Elastic notes that data streams support only the create action.",
          "output": "HiveSilo audit events as documents in your index or data stream.",
          "sourceIds": [
            "P719-D01"
          ]
        },
        {
          "heading": "An API key with one job.",
          "body": "Elasticsearch accepts an API key in the Authorization header. The create action needs only the create_doc, create, index or write index privilege on the target, so the key can be limited to adding documents.",
          "output": "A narrow credential you create and can delete.",
          "sourceIds": [
            "P719-D01",
            "P719-D02",
            "P719-D04"
          ]
        },
        {
          "heading": "Fields in the Elastic Common Schema.",
          "body": "ECS defines common fields for event data, and Elastic Security requires @timestamp, ecs.version, event.kind, event.category and event.type on all data. Details with no ECS equivalent can be nested under a proper name, as ECS suggests, and the mapping is agreed at setup.",
          "output": "Audit events that Elastic Security can read.",
          "sourceIds": [
            "P719-D06",
            "P719-D09",
            "P719-D10"
          ]
        }
      ]
    },
    "integration": {
      "heading": "How HiveSilo connects to Elastic",
      "statusNote": "The Elastic connection is available and is activated for each client on request, against that client's own Elasticsearch deployment, with the API key, index or data stream and privileges their administrator approves.",
      "intro": "Every row below names a route in Elastic's public documentation. HiveSilo calls the Elasticsearch Bulk API outbound to add documents. It does not search or read your cluster, and it does not ask Elastic to call into your systems. These are HiveSilo's own audit and security events for your tenant, not visitor or lead data.",
      "tableCaption": "What HiveSilo sends to Elastic and the documented route for each item",
      "columns": [
        "HiveSilo sends",
        "How Elastic receives it",
        "Documented route"
      ],
      "flows": [
        {
          "sends": "Administrative and access actions in your HiveSilo tenant",
          "lands": "Documents in the index or data stream you name",
          "route": "POST /_bulk or POST /{index}/_bulk with a newline delimited JSON body and an \"Authorization: ApiKey\" header.",
          "sourceIds": [
            "P719-D01",
            "P719-D02"
          ]
        },
        {
          "sends": "Data-rights requests recorded for your tenant",
          "lands": "Documents added with the create action",
          "route": "Data streams support only the create action, which needs the create_doc, create, index or write index privilege.",
          "sourceIds": [
            "P719-D01"
          ]
        },
        {
          "sends": "Traffic-protection alerts",
          "lands": "Documents categorized with ECS event fields",
          "route": "ECS defines event.kind, event.category, event.type and event.outcome as its categorization fields, with event.action for the specific action.",
          "sourceIds": [
            "P719-D07",
            "P719-D08"
          ]
        },
        {
          "sends": "Event details that have no matching ECS field",
          "lands": "Custom fields beside the ECS fields",
          "route": "ECS allows custom fields and describes nesting them under a proper name as a relatively safe approach.",
          "sourceIds": [
            "P719-D09"
          ]
        }
      ],
      "facts": [
        {
          "label": "Access you grant",
          "body": "An Elasticsearch API key, created with POST /_security/api_key or in Kibana and sent in the Authorization header. To add documents the key needs the create_doc, create, index or write index privilege on the target.",
          "sourceIds": [
            "P719-D01",
            "P719-D02",
            "P719-D03"
          ]
        },
        {
          "label": "Key lifetime",
          "body": "Elastic states that API keys never expire by default and that an expiration can be set when the key is created. A personal key created from the Kibana Connection details panel has a default expiration of 90 days.",
          "sourceIds": [
            "P719-D03",
            "P719-D04"
          ]
        },
        {
          "label": "Limits to plan for",
          "body": "Elasticsearch limits an HTTP request body to 100mb by default (http.max_content_length). Elastic states there is no \"correct\" number of actions for a single bulk request.",
          "sourceIds": [
            "P719-D01",
            "P719-D05"
          ]
        },
        {
          "label": "Schema guidance",
          "body": "The Elastic Common Schema is the documented field set for event data. Elastic Security requires data normalized to ECS, with @timestamp, ecs.version, event.kind, event.category and event.type always present.",
          "sourceIds": [
            "P719-D06",
            "P719-D10"
          ]
        },
        {
          "label": "How to revoke",
          "body": "Delete the API key on the Kibana API keys page. Elastic documents that deleting keys needs the manage_api_key or manage_own_api_key privilege.",
          "sourceIds": [
            "P719-D04"
          ]
        },
        {
          "label": "No package claimed",
          "body": "Published Elastic integrations are packages added to the integrations repository by pull request. HiveSilo does not claim one. This connection is an API key and the documented Bulk API.",
          "sourceIds": [
            "P719-D11"
          ]
        }
      ],
      "questionsHeading": "Who, what, when, where, how and why",
      "questions": [
        {
          "label": "Who",
          "body": "Security and platform teams that run Elasticsearch, Kibana and Elastic Security and want a software vendor's audit trail in the same cluster. Your Elastic administrator creates the API key.",
          "sourceIds": [
            "P719-D03",
            "P719-D04"
          ]
        },
        {
          "label": "What",
          "body": "HiveSilo's audit and security events for your tenant: administrative and access actions, data-rights requests, and traffic-protection alerts. Each says what happened, when and how severe it was, with a hashed reference to who or what was involved. The event layout is shared under agreement during setup.",
          "sourceIds": [
            "P719-D07",
            "HS3"
          ]
        },
        {
          "label": "When",
          "body": "When one of those events is recorded in your HiveSilo tenant, after the connection has been activated for you.",
          "sourceIds": [
            "HS2"
          ]
        },
        {
          "label": "Where",
          "body": "In your own Elasticsearch deployment, in the index or data stream you name. Your roles and lifecycle settings apply.",
          "sourceIds": [
            "P719-D01"
          ]
        },
        {
          "label": "How",
          "body": "Outbound HTTPS requests to the Bulk API on your deployment address, authenticated with an API key in the Authorization header.",
          "sourceIds": [
            "P719-D01",
            "P719-D02"
          ]
        },
        {
          "label": "Why",
          "body": "Elastic is where your team already investigates. Writing HiveSilo events there in ECS lets existing searches and Elastic Security views include them.",
          "sourceIds": [
            "P719-D06",
            "P719-D10",
            "HS3"
          ]
        }
      ],
      "summary": "Elastic is where your security team searches and investigates. HiveSilo sends its own audit and security events for your tenant to your Elasticsearch deployment through the documented Bulk API, with fields that follow the Elastic Common Schema and an API key your administrator creates and can delete. The connection is available and is activated for each client on request. Events carry hashed identifiers and no visitor or lead data; customer identities stay in your own confidential environment.",
      "summarySourceIds": [
        "P719-D01",
        "P719-D06",
        "HSF1",
        "HS4"
      ],
      "features": {
        "heading": "Where each HiveSilo capability meets Elastic",
        "intro": "Each row pairs a published HiveSilo capability with the Elastic feature that receives or uses its audit trail. HiveSilo only adds documents with an API key. Pipelines, rules, roles and retention are configured by your team in your own deployment.",
        "rows": [
          {
            "capability": "AI Governance & Control",
            "feature": "ECS event fields, including event.action and event.outcome",
            "gain": "The people who hold authority over AI-assisted actions work in your HiveSilo tenant. Their administrative and access actions arrive in the field set your searches already use, while HiveSilo keeps its own append-only record of governed decisions.",
            "sourceIds": [
              "P719-D07",
              "P719-D08",
              "HS6",
              "HSF1"
            ]
          },
          {
            "capability": "AI firewall, bot defense and site protection",
            "feature": "Elastic Security detection rules",
            "gain": "Traffic-protection alerts from HiveSilo are documents the detection engine can evaluate, so bot activity against your site can generate an alert under rules you write.",
            "sourceIds": [
              "P719-D10",
              "P719-D15",
              "HSF1"
            ]
          },
          {
            "capability": "Client-controlled privacy and verification",
            "feature": "An API key limited to the create_doc index privilege",
            "gain": "Access is one key you create and can delete. Elastic documents that create_doc does not allow updating or overwriting existing documents. The events hold hashed identifiers with no visitor or lead data.",
            "sourceIds": [
              "P719-D03",
              "P719-D16",
              "HS4",
              "HSF1"
            ]
          },
          {
            "capability": "Client-controlled privacy and verification",
            "feature": "The read index privilege, granted through your own roles",
            "gain": "Your roles decide who can search the HiveSilo audit trail, so vendor activity can be verified without widening cluster access.",
            "sourceIds": [
              "P719-D16",
              "HS3"
            ]
          },
          {
            "capability": "Business insights and oversight",
            "feature": "Ingest pipelines and their processors",
            "gain": "If you want extra fields or your own naming, a pipeline you control can transform HiveSilo events before they are indexed.",
            "sourceIds": [
              "P719-D12",
              "HSF1"
            ]
          },
          {
            "capability": "Business insights and oversight",
            "feature": "Data streams with a data stream lifecycle retention period",
            "gain": "The HiveSilo audit trail is kept for at least the retention time your own policy defines, in a stream built for append-only event data.",
            "sourceIds": [
              "P719-D13",
              "P719-D14",
              "HSF1"
            ]
          }
        ]
      },
      "capture": {
        "heading": "What generates the events, and what they leave out",
        "paragraphs": [
          "The events come from HiveSilo's own platform, not from your visitors. One is recorded when someone performs an administrative or access action in your HiveSilo tenant, when a data-rights request is logged for your tenant, or when bot defense raises a traffic-protection alert for your site. Nothing is installed in your cluster to produce them, and no Elastic Agent is involved.",
          "Each event says what happened, when and how severe it was, with a hashed reference to who or what was involved. It carries no visitor or lead data. The event layout is shared under agreement during setup. Customer identities stay in your own confidential environment, outside HiveSilo's visibility, and never enter this feed. HiveSilo writes these events to your Elasticsearch deployment and does not read anything back."
        ],
        "sourceIds": [
          "HS3",
          "HS4",
          "HSF1"
        ]
      },
      "setup": {
        "heading": "What your Elastic team does",
        "intro": "The connection is configuration in your Elastic deployment plus activation on the HiveSilo side. These are the steps on your side.",
        "steps": [
          {
            "title": "Create the target.",
            "body": "Name the index or data stream that will hold HiveSilo events. A data stream needs a matching index template, and every document carries a @timestamp field.",
            "sourceIds": [
              "P719-D13"
            ]
          },
          {
            "title": "Set retention.",
            "body": "For a data stream, configure the data stream lifecycle with the retention period your audit policy requires.",
            "sourceIds": [
              "P719-D14"
            ]
          },
          {
            "title": "Create a narrow API key.",
            "body": "Create the key in Kibana or with POST /_security/api_key, limited to the create_doc privilege on that one target, with an expiration that suits your rotation practice.",
            "sourceIds": [
              "P719-D03",
              "P719-D04",
              "P719-D16"
            ]
          },
          {
            "title": "Test any ingest pipeline first.",
            "body": "If you add an ingest pipeline for these events, Elastic recommends testing it with sample documents before production, in Kibana or with the simulate pipeline API.",
            "sourceIds": [
              "P719-D12"
            ]
          },
          {
            "title": "Share the address and key.",
            "body": "Give HiveSilo your deployment address, the target name and the encoded key. Requests send it as \"Authorization: ApiKey\".",
            "sourceIds": [
              "P719-D02"
            ]
          },
          {
            "title": "Add detection rules and roles.",
            "body": "Write Elastic Security detection rules on the events that matter to you, validate them before enabling as Elastic suggests, and grant the read privilege only to the roles that should search the data.",
            "sourceIds": [
              "P719-D15",
              "P719-D16"
            ]
          }
        ],
        "timeline": "HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The Elastic steps above run on your own change process.",
        "timelineSourceIds": [
          "HSF1"
        ]
      },
      "preview": {
        "heading": "What your analyst sees",
        "note": "Illustrative example, not an Elastic or Kibana screen. The index or data stream is chosen by your administrator. Labels are plain words; the event layout and any field mapping are agreed at setup. The reference is a hashed placeholder.",
        "sourceIds": [],
        "fields": [
          {
            "label": "What happened",
            "value": "An administrator changed a tenant setting"
          },
          {
            "label": "Severity",
            "value": "Medium"
          },
          {
            "label": "Time",
            "value": "2026-11-11T02:14:07Z"
          },
          {
            "label": "Reference",
            "value": "a1b2… (hashed)"
          }
        ],
        "task": {
          "label": "Document detail",
          "subject": "Administrative change recorded in your HiveSilo tenant",
          "body": "No visitor or lead data is present. How the event maps to ECS fields is agreed at setup, and your own detection rule decides whether this raises an alert."
        }
      }
    },
    "example": {
      "heading": "Access to your tenant changes. Is it on the record?",
      "setup": "Illustrative workflow: an access change is made in your HiveSilo tenant. Your security team reviews access changes across all vendors each week in Kibana.",
      "nativeBaseline": "Elasticsearch stores the document and Kibana and Elastic Security query it with your other sources. Your index templates, lifecycle policies and detection rules stay as configured.",
      "inputs": [
        "The HiveSilo audit event: what happened, when and how severe it was, with a hashed reference to who or what was involved.",
        "The index or data stream and the ECS fields on the document.",
        "Your own saved searches and detection rules for access change."
      ],
      "decision": "The reviewer finds the change in the weekly search and confirms it against an approved request.",
      "output": "A document in your cluster that searches, dashboards and detection rules can use.",
      "owner": "Your security team owns the review and any rule that runs on the data. HiveSilo supplies the event; it does not create or change rules in Elastic Security.",
      "hold": "If Elasticsearch rejects the request, for example because the key lacks the index privilege, treat the feed as interrupted until the key or target is corrected.",
      "record": "Keep the document under the lifecycle policy you set for that index or data stream.",
      "sourceIds": [
        "P719-D01",
        "P719-D08",
        "P719-D10"
      ]
    },
    "governance": {
      "intro": "Give the key the least it needs: add documents to one target.",
      "example": "Create an API key used only for the HiveSilo feed, with the create_doc privilege on one index or data stream and nothing else. Set an expiration that matches your rotation practice and name an owner for renewal. Agree in advance which ECS category values the events use, and leave a categorization field empty where no published value fits, as ECS advises."
    },
    "privacy": {
      "intro": "These are HiveSilo's own audit and security events, not your visitors or leads.",
      "detail": "Each event describes an action in your HiveSilo tenant: what happened, when and how severe it was, with a hashed reference to who or what was involved. Visitor and lead data is not part of this feed. Customer identities stay in the environment you control. Once a document is in your cluster, your Elasticsearch roles and lifecycle settings govern who can read it and for how long."
    },
    "outcomes": {
      "intro": "HiveSilo scores buyers on your website. The Elastic connection gives your security team the audit trail of how that system is administered.",
      "panels": [
        "Buyer scoring runs on your own website, and Elastic shows your security team who administered it.",
        "Bring more sites onto what works while the same Elastic searches cover each one.",
        "Retire a separate vendor log review by querying HiveSilo audit events in Elastic.",
        "Index traffic-protection alerts about bots and invalid traffic where your Elastic detections can read them.",
        "Use the audit documents in Elastic to show how the data behind your revenue decisions was accessed and handled."
      ]
    },
    "fit": {
      "intro": "Most useful where Elastic is the security team's system of record and vendor audit trails are expected in the cluster.",
      "good": [
        "Organizations that run Elasticsearch with Kibana or Elastic Security for investigation.",
        "Teams with audit or retention obligations that cover software vendors.",
        "Teams able to name the index or data stream, the key owner and the ECS mapping for a new source."
      ],
      "consider": [
        "Your deployment address must be reachable for outbound calls from HiveSilo.",
        "Index templates and lifecycle policies for the target are set up by your team.",
        "The feed carries audit and security events only. Buyer scores and leads go to your CRM or warehouse, not to Elastic."
      ]
    },
    "connection": {
      "heading": "Agree the deployment address, the key and the target.",
      "paragraphs": [
        "Your Elastic administrator names the index or data stream, creates an API key limited to adding documents there, and shares the address of your Elasticsearch deployment. HiveSilo stores the key for your tenant and writes only to that target.",
        "The connection is available and is activated for each client on request. Public documentation establishes what the Bulk API and ECS support; your Elastic configuration and your agreement with HiveSilo determine the scope that is switched on."
      ],
      "sourceIds": [
        "P719-D01",
        "P719-D03",
        "P719-D04",
        "HS10"
      ]
    },
    "faqs": [
      {
        "question": "Does HiveSilo connect to Elastic?",
        "answer": "Yes. The Elastic connection is available and is activated for each client on request. It uses the documented Elasticsearch Bulk API with an API key your administrator creates.",
        "sourceIds": [
          "P719-D01",
          "HS2"
        ]
      },
      {
        "question": "What does HiveSilo send to Elastic, and does it read anything back?",
        "answer": "It sends its own audit and security events for your tenant: administrative and access actions, data-rights requests, and traffic-protection alerts. Each says what happened, when and how severe it was, with a hashed reference to who or what was involved. It is not visitor or lead data. The event layout is shared under agreement during setup. HiveSilo only adds documents. Searching needs the read privilege, which is separate from create_doc and which this connection does not ask for.",
        "sourceIds": [
          "P719-D07",
          "P719-D16",
          "HS3"
        ]
      },
      {
        "question": "Which Elastic products and features are in scope?",
        "answer": "Elasticsearch receives the documents through the Bulk API, into an index or data stream. Kibana manages the API key and searches the data. Elastic Security can read the events because they carry the ECS fields it requires, and its detection rules can alert on them. Ingest pipelines and data stream lifecycle retention are yours to add. HiveSilo configures none of those; it supplies the events.",
        "sourceIds": [
          "P719-D01",
          "P719-D04",
          "P719-D10",
          "P719-D12",
          "P719-D14",
          "P719-D15"
        ]
      },
      {
        "question": "Which endpoint does it use, and can we test first?",
        "answer": "POST /_bulk or POST /{index}/_bulk, with a newline delimited JSON body. For a data stream the action is create, which is the only action data streams support. If you put an ingest pipeline in front of the target, Elastic documents a simulate pipeline API and a Kibana test with sample documents, and it suggests validating detection rules before enabling them.",
        "sourceIds": [
          "P719-D01",
          "P719-D12",
          "P719-D15"
        ]
      },
      {
        "question": "What privileges does the API key need?",
        "answer": "For the create action, Elastic lists the create_doc, create, index or write index privilege on the target. The key is sent as \"Authorization: ApiKey\" with the encoded value.",
        "sourceIds": [
          "P719-D01",
          "P719-D02"
        ]
      },
      {
        "question": "Do the events follow the Elastic Common Schema?",
        "answer": "ECS is the documented field set. Elastic Security requires @timestamp, ecs.version, event.kind, event.category and event.type on all data, and ECS allows vendor fields nested under a proper name. How HiveSilo events map to ECS is agreed at setup.",
        "sourceIds": [
          "P719-D06",
          "P719-D09",
          "P719-D10"
        ]
      },
      {
        "question": "How do we stop the feed?",
        "answer": "Delete the API key in Kibana, which needs the manage_api_key or manage_own_api_key privilege. You can also set an expiration when the key is created, or ask HiveSilo to switch the connection off.",
        "sourceIds": [
          "P719-D03",
          "P719-D04"
        ]
      },
      {
        "question": "Is there a HiveSilo integration package for Elastic?",
        "answer": "No package or listing is claimed. Elastic publishes integrations through its integrations repository. This connection needs none: it is an API key and the documented Bulk API.",
        "sourceIds": [
          "P719-D11"
        ]
      }
    ],
    "relationshipContext": {
      "privacyContext": "The feed carries HiveSilo's audit and security events for your tenant, with hashed identifiers. It does not carry visitor or lead data. Customer identities stay in the environment you control, and Elasticsearch roles govern who can read the documents.",
      "diagramLabels": [
        "Customer identities stay in your environment",
        "HiveSilo audit and security events, hashed identifiers",
        "Your Elasticsearch index, under your API key"
      ],
      "reviewIntentSentences": [
        "An Elastic review should start with the indices, detection rules and lifecycle policies your team already runs.",
        "An Elastic review of the connection should confirm the API key, its index privilege and its expiration.",
        "When reviewing Elastic with HiveSilo, ask which ECS category values the audit events should carry."
      ],
      "sourceIds": [
        "P719-D01",
        "P719-D04",
        "HS3",
        "HS4"
      ]
    }
  },
  "shared": {
    "privacyModel": "Customer identities and re-identifiable data stay in the customer-controlled environment; only permitted non-PII signals and scores cross the configured boundary. Account, billing and support records are separate.",
    "governanceSteps": [
      {
        "title": "Request",
        "detail": "An AI proposes an action"
      },
      {
        "title": "Check",
        "detail": "Policy and authority"
      },
      {
        "title": "Approve",
        "detail": "Named owner, when required"
      },
      {
        "title": "Act",
        "detail": "Within permitted scope"
      },
      {
        "title": "Record",
        "detail": "Keep the action, outcome and accountable owner traceable."
      }
    ],
    "outcomes": [
      {
        "value": "3,790",
        "prefix": "",
        "suffix": "of 5,000",
        "label": "UHNW buyer score",
        "note": "Illustrative score"
      },
      {
        "value": "4–6×",
        "prefix": "",
        "suffix": "",
        "label": "Reported conversion lift",
        "note": "Closed-revenue outcomes"
      },
      {
        "value": "31%",
        "prefix": "Up to",
        "suffix": "",
        "label": "Reported ad-spend savings",
        "note": "Bot and invalid-traffic filtering"
      },
      {
        "value": "99.9999%",
        "prefix": "",
        "suffix": "",
        "label": "Bot detection",
        "note": "Observed client results"
      },
      {
        "value": "5–21%",
        "prefix": "",
        "suffix": "",
        "label": "Revenue lift from existing data",
        "note": "HiveSilo-reported client results"
      }
    ],
    "outcomeContext": "Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary.",
    "botDetectionGoal": "99.9999999% is a goal, not an achieved result."
  },
  "sources": [
    {
      "id": "P719-D01",
      "title": "Elasticsearch API: Bulk index or delete documents",
      "url": "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk",
      "supports": "POST /_bulk and POST /{index}/_bulk perform multiple actions in one request with a newline delimited JSON (NDJSON) body whose final line ends with a newline; the create action needs the create_doc, create, index or write index privilege; data streams support only the create action; there is no \"correct\" number of actions per request.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D02",
      "title": "Elasticsearch API documentation: Authentication",
      "url": "https://www.elastic.co/docs/api/doc/elasticsearch/authentication",
      "supports": "The API accepts bearer, basic and API key authentication; an API key is sent as \"Authorization: ApiKey\" with the encoded value, and keys come from the /_security/api_key APIs.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D03",
      "title": "Elasticsearch API: Create an API key",
      "url": "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-api-key",
      "supports": "POST /_security/api_key creates an API key; by default API keys never expire and an expiration can be set at creation; the call requires the manage_own_api_key cluster privilege.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D04",
      "title": "Elastic Docs: Elasticsearch API keys",
      "url": "https://www.elastic.co/docs/deploy-manage/api-keys/elasticsearch-api-keys",
      "supports": "API keys are managed in Kibana; using them there needs the manage_security, manage_api_key or manage_own_api_key cluster privilege, and deleting keys needs manage_api_key or manage_own_api_key; a personal key created from the Connection details panel has a default expiration of 90 days.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D05",
      "title": "Elasticsearch Reference: Networking settings",
      "url": "https://www.elastic.co/docs/reference/elasticsearch/configuration-reference/networking-settings",
      "supports": "http.max_content_length is the maximum size of an HTTP request body and defaults to 100mb.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D06",
      "title": "Elastic Common Schema (ECS) reference",
      "url": "https://www.elastic.co/docs/reference/ecs",
      "supports": "ECS is an open source specification that defines a common set of fields for storing event data, such as logs and metrics, in Elasticsearch.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D07",
      "title": "Elastic Common Schema: Event fields",
      "url": "https://www.elastic.co/docs/reference/ecs/ecs-event",
      "supports": "Defines the event field set, including event.action (the action captured by the event) and event.outcome (whether the event represents a success or a failure).",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D08",
      "title": "Elastic Common Schema: ECS categorization fields",
      "url": "https://www.elastic.co/docs/reference/ecs/ecs-category-field-values-reference",
      "supports": "ECS defines four categorization fields: event.kind, event.category, event.type and event.outcome. Events that match no published value should leave the fields empty.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D09",
      "title": "Elastic Common Schema: Custom fields",
      "url": "https://www.elastic.co/docs/reference/ecs/ecs-custom-fields-in-ecs",
      "supports": "Custom fields are allowed alongside ECS; nesting custom fields under a proper name, such as a company name, is described as a relatively safe approach.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D10",
      "title": "Elastic Security ECS field reference",
      "url": "https://www.elastic.co/docs/reference/security/fields-and-object-schemas/siem-field-reference",
      "supports": "Elastic Security requires event data to be normalized to ECS; all data must contain @timestamp, ecs.version, event.kind, event.category and event.type.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D11",
      "title": "Elastic Docs: Publish an integration via Pull Request",
      "url": "https://www.elastic.co/docs/extend/integrations/_publish_an_integration",
      "supports": "A published Elastic integration is a package added to the integrations repository by pull request and released to the package registry. HiveSilo does not claim an Elastic integration package.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D12",
      "title": "Elastic Docs: Elasticsearch ingest pipelines",
      "url": "https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines",
      "supports": "Ingest pipelines perform transformations on data before indexing through processors that run sequentially; managing them needs the manage_pipeline cluster privilege; Elastic recommends testing a pipeline with sample documents in Kibana or with the simulate pipeline API (POST _ingest/pipeline/_simulate); index.default_pipeline sets a default pipeline.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D13",
      "title": "Elastic Docs: Data streams in Elasticsearch",
      "url": "https://www.elastic.co/docs/manage-data/data-store/data-streams",
      "supports": "A data stream is a single named resource over backing indices optimized for append-only time series data such as logs and events; it requires a matching index template, and every document must contain a @timestamp field.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D14",
      "title": "Elastic Docs: Data stream lifecycle in Elasticsearch",
      "url": "https://www.elastic.co/docs/manage-data/lifecycle/data-stream",
      "supports": "Data stream lifecycle manages retention: data is kept at least for the retention time defined and data older than the retention period is deleted automatically later; retention can be configured on the data stream level or on a global level.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D15",
      "title": "Elastic Docs: Detections and alerts",
      "url": "https://www.elastic.co/docs/solutions/security/detect-and-alert",
      "supports": "Elastic Security's detection engine evaluates data against detection rules and generates alerts when rule criteria are met; the suggested lifecycle includes validating rule logic against historical data before enabling.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P719-D16",
      "title": "Elasticsearch Reference: Elasticsearch privileges",
      "url": "https://www.elastic.co/docs/reference/elasticsearch/security-privileges",
      "supports": "The create_doc index privilege allows indexing documents and does not grant permission to update or overwrite existing documents; the read index privilege gives read-only access to actions such as search and get.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HSF1",
      "title": "HiveSilo capability overview",
      "url": "https://hivesilo.com/evidence/features.md",
      "supports": "Published HiveSilo capabilities relied on here: AI Governance & Control, AI firewall, bot defense and site protection, business insights and oversight, and client-controlled privacy and verification; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HS0",
      "title": "HiveSilo: industry coverage",
      "url": "https://hivesilo.com",
      "supports": "First-party description of buyer intelligence across 12 luxury niches.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS1",
      "title": "HiveSilo: platform",
      "url": "https://hivesilo.com/platform",
      "supports": "Published intent, sales-prioritization and traffic-quality capabilities.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS2",
      "title": "HiveSilo: integration scope",
      "url": "https://hivesilo.com/integrations",
      "supports": "Named destinations, scoped activation and customer-controlled dispatch.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS3",
      "title": "HiveSilo: security architecture",
      "url": "https://hivesilo.com/security-architecture",
      "supports": "Documented confidential processing, BYOK and customer control.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS4",
      "title": "HiveSilo: data handling",
      "url": "https://hivesilo.com/data-handling",
      "supports": "Customer identity custody, pseudonymous-data boundaries and separate account records.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS5",
      "title": "HiveSilo: published outcomes",
      "url": "https://hivesilo.com/case-studies",
      "supports": "Existing first-party outcomes material, with client-reported and illustrative descriptions.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS6",
      "title": "HiveSilo: AI agentic governance",
      "url": "https://hivesilo.com/ai-agentic-governance",
      "supports": "Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS7",
      "title": "HiveSilo: AI implementation layer",
      "url": "https://hivesilo.com/ai-implementation-layer",
      "supports": "Published combined implementation model for intelligence, confidential processing and AI governance.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS8",
      "title": "HiveSilo: bot-detection results and buyer-score specimen",
      "url": "https://hivesilo.com/",
      "supports": "The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS9",
      "title": "HiveSilo: owned-data revenue result briefing",
      "url": "https://hivesilo.com/contact",
      "supports": "HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows on 25 October 2026.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS10",
      "title": "HiveSilo: enterprise agreements and responsibility",
      "url": "https://hivesilo.com/terms",
      "supports": "Signed enterprise agreements govern the engagement and take precedence over website summaries.",
      "reviewed": "2026-10-26"
    }
  ],
  "articleText": "Enterprise key management & security monitoring Elastic + HiveSilo Available View scope HiveSilo / Integrations / Elastic Elastic. HiveSilo audit events as documents in your own cluster. Elastic is where your team searches and investigates. HiveSilo writes its own audit and security events for your tenant to your Elasticsearch deployment through the Bulk API, with an API key you create. Contact HiveSilo Explore the fit Start with a conversation. No client records needed. Your cluster, your index. A vendor audit trail in it. Your client list stays yours. The value AI control Your data What you could gain Let’s talk FAQs & evidence Your evidence is in Elasticsearch. Is your vendor's? Elastic can search and detect on the documents it stores. A vendor's administrative history is not among them until it is indexed. What makes a vendor audit feed usable in Elastic? Teams on Elastic build detections, dashboards and saved searches over their indices and data streams. A vendor log that stays in a vendor console cannot be queried with the rest, and it follows a retention policy the team did not set. Elastic already provides the indexing, the security model and the schema. HiveSilo supplies the events: administrative and access actions in your HiveSilo tenant, data-rights requests, and traffic-protection alerts. They are written as documents to the index or data stream you name, on the deployment address you provide, and your own roles and lifecycle settings apply from there. An Elastic review should start with the indices, detection rules and lifecycle policies your team already runs. [P719-D01] [P719-D04] [HS3] [HS4] Search HiveSilo activity with the queries you already have. HiveSilo does not add a console for your analysts. It writes tenant audit and security events to Elasticsearch, so Kibana and Elastic Security can read them like any other source. Talk through your use case Who acted and how. Query HiveSilo administrative and access actions beside events from your other systems. Where it is stored. Choose the index or data stream, and the lifecycle that applies to it. What the key can do. Limit the API key to writing documents to that one target. Available The Elastic connection is available and is activated for each client on request, against that client's own Elasticsearch deployment, with the API key, index or data stream and privileges their administrator approves. How HiveSilo connects to Elastic Elastic is where your security team searches and investigates. HiveSilo sends its own audit and security events for your tenant to your Elasticsearch deployment through the documented Bulk API, with fields that follow the Elastic Common Schema and an API key your administrator creates and can delete. The connection is available and is activated for each client on request. Events carry hashed identifiers and no visitor or lead data; customer identities stay in your own confidential environment. [P719-D01] [P719-D06] [HSF1] [HS4] What your analyst sees What happened An administrator changed a tenant setting Severity Medium Time 2026-11-11T02:14:07Z Reference a1b2… (hashed) Document detail Administrative change recorded in your HiveSilo tenant No visitor or lead data is present. How the event maps to ECS fields is agreed at setup, and your own detection rule decides whether this raises an alert. Illustrative example, not an Elastic or Kibana screen. The index or data stream is chosen by your administrator. Labels are plain words; the event layout and any field mapping are agreed at setup. The reference is a hashed placeholder. What HiveSilo sends and the route Elastic documents Every row below names a route in Elastic's public documentation. HiveSilo calls the Elasticsearch Bulk API outbound to add documents. It does not search or read your cluster, and it does not ask Elastic to call into your systems. These are HiveSilo's own audit and security events for your tenant, not visitor or lead data. What HiveSilo sends to Elastic and the documented route for each item HiveSilo sends How Elastic receives it Documented route Administrative and access actions in your HiveSilo tenant Documents in the index or data stream you name POST /_bulk or POST /{index}/_bulk with a newline delimited JSON body and an \"Authorization: ApiKey\" header. [P719-D01] [P719-D02] Data-rights requests recorded for your tenant Documents added with the create action Data streams support only the create action, which needs the create_doc, create, index or write index privilege. [P719-D01] Traffic-protection alerts Documents categorized with ECS event fields ECS defines event.kind, event.category, event.type and event.outcome as its categorization fields, with event.action for the specific action. [P719-D07] [P719-D08] Event details that have no matching ECS field Custom fields beside the ECS fields ECS allows custom fields and describes nesting them under a proper name as a relatively safe approach. [P719-D09] Access you grant An Elasticsearch API key, created with POST /_security/api_key or in Kibana and sent in the Authorization header. To add documents the key needs the create_doc, create, index or write index privilege on the target. [P719-D01] [P719-D02] [P719-D03] Key lifetime Elastic states that API keys never expire by default and that an expiration can be set when the key is created. A personal key created from the Kibana Connection details panel has a default expiration of 90 days. [P719-D03] [P719-D04] Limits to plan for Elasticsearch limits an HTTP request body to 100mb by default (http.max_content_length). Elastic states there is no \"correct\" number of actions for a single bulk request. [P719-D01] [P719-D05] Schema guidance The Elastic Common Schema is the documented field set for event data. Elastic Security requires data normalized to ECS, with @timestamp, ecs.version, event.kind, event.category and event.type always present. [P719-D06] [P719-D10] How to revoke Delete the API key on the Kibana API keys page. Elastic documents that deleting keys needs the manage_api_key or manage_own_api_key privilege. [P719-D04] No package claimed Published Elastic integrations are packages added to the integrations repository by pull request. HiveSilo does not claim one. This connection is an API key and the documented Bulk API. [P719-D11] Where each HiveSilo capability meets Elastic Each row pairs a published HiveSilo capability with the Elastic feature that receives or uses its audit trail. HiveSilo only adds documents with an API key. Pipelines, rules, roles and retention are configured by your team in your own deployment. Where each HiveSilo capability meets Elastic HiveSilo capability Elastic feature it works with What you gain AI Governance & Control ECS event fields, including event.action and event.outcome The people who hold authority over AI-assisted actions work in your HiveSilo tenant. Their administrative and access actions arrive in the field set your searches already use, while HiveSilo keeps its own append-only record of governed decisions. [P719-D07] [P719-D08] [HS6] [HSF1] AI firewall, bot defense and site protection Elastic Security detection rules Traffic-protection alerts from HiveSilo are documents the detection engine can evaluate, so bot activity against your site can generate an alert under rules you write. [P719-D10] [P719-D15] [HSF1] Client-controlled privacy and verification An API key limited to the create_doc index privilege Access is one key you create and can delete. Elastic documents that create_doc does not allow updating or overwriting existing documents. The events hold hashed identifiers with no visitor or lead data. [P719-D03] [P719-D16] [HS4] [HSF1] Client-controlled privacy and verification The read index privilege, granted through your own roles Your roles decide who can search the HiveSilo audit trail, so vendor activity can be verified without widening cluster access. [P719-D16] [HS3] Business insights and oversight Ingest pipelines and their processors If you want extra fields or your own naming, a pipeline you control can transform HiveSilo events before they are indexed. [P719-D12] [HSF1] Business insights and oversight Data streams with a data stream lifecycle retention period The HiveSilo audit trail is kept for at least the retention time your own policy defines, in a stream built for append-only event data. [P719-D13] [P719-D14] [HSF1] What generates the events, and what they leave out The events come from HiveSilo's own platform, not from your visitors. One is recorded when someone performs an administrative or access action in your HiveSilo tenant, when a data-rights request is logged for your tenant, or when bot defense raises a traffic-protection alert for your site. Nothing is installed in your cluster to produce them, and no Elastic Agent is involved. Each event says what happened, when and how severe it was, with a hashed reference to who or what was involved. It carries no visitor or lead data. The event layout is shared under agreement during setup. Customer identities stay in your own confidential environment, outside HiveSilo's visibility, and never enter this feed. HiveSilo writes these events to your Elasticsearch deployment and does not read anything back. [HS3] [HS4] [HSF1] What your Elastic team does The connection is configuration in your Elastic deployment plus activation on the HiveSilo side. These are the steps on your side. Create the target. Name the index or data stream that will hold HiveSilo events. A data stream needs a matching index template, and every document carries a @timestamp field. [P719-D13] Set retention. For a data stream, configure the data stream lifecycle with the retention period your audit policy requires. [P719-D14] Create a narrow API key. Create the key in Kibana or with POST /_security/api_key, limited to the create_doc privilege on that one target, with an expiration that suits your rotation practice. [P719-D03] [P719-D04] [P719-D16] Test any ingest pipeline first. If you add an ingest pipeline for these events, Elastic recommends testing it with sample documents before production, in Kibana or with the simulate pipeline API. [P719-D12] Share the address and key. Give HiveSilo your deployment address, the target name and the encoded key. Requests send it as \"Authorization: ApiKey\". [P719-D02] Add detection rules and roles. Write Elastic Security detection rules on the events that matter to you, validate them before enabling as Elastic suggests, and grant the read privilege only to the roles that should search the data. [P719-D15] [P719-D16] HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The Elastic steps above run on your own change process. [HSF1] Who, what, when, where, how and why Who Security and platform teams that run Elasticsearch, Kibana and Elastic Security and want a software vendor's audit trail in the same cluster. Your Elastic administrator creates the API key. [P719-D03] [P719-D04] What HiveSilo's audit and security events for your tenant: administrative and access actions, data-rights requests, and traffic-protection alerts. Each says what happened, when and how severe it was, with a hashed reference to who or what was involved. The event layout is shared under agreement during setup. [P719-D07] [HS3] When When one of those events is recorded in your HiveSilo tenant, after the connection has been activated for you. [HS2] Where In your own Elasticsearch deployment, in the index or data stream you name. Your roles and lifecycle settings apply. [P719-D01] How Outbound HTTPS requests to the Bulk API on your deployment address, authenticated with an API key in the Authorization header. [P719-D01] [P719-D02] Why Elastic is where your team already investigates. Writing HiveSilo events there in ECS lets existing searches and Elastic Security views include them. [P719-D06] [P719-D10] [HS3] See the intelligence behind the next move Documents through the Bulk API. HiveSilo sends events in the newline delimited JSON format the Bulk API documents, to POST /_bulk or POST /{index}/_bulk on your deployment. Elastic notes that data streams support only the create action. [P719-D01] Useful output: HiveSilo audit events as documents in your index or data stream. An API key with one job. Elasticsearch accepts an API key in the Authorization header. The create action needs only the create_doc, create, index or write index privilege on the target, so the key can be limited to adding documents. [P719-D01] [P719-D02] [P719-D04] Useful output: A narrow credential you create and can delete. Fields in the Elastic Common Schema. ECS defines common fields for event data, and Elastic Security requires @timestamp, ecs.version, event.kind, event.category and event.type on all data. Details with no ECS equivalent can be nested under a proper name, as ECS suggests, and the mapping is agreed at setup. [P719-D06] [P719-D09] [P719-D10] Useful output: Audit events that Elastic Security can read. Access to your tenant changes. Is it on the record? Illustrative workflow: an access change is made in your HiveSilo tenant. Your security team reviews access changes across all vendors each week in Kibana. Start with Elastic Elasticsearch stores the document and Kibana and Elastic Security query it with your other sources. Your index templates, lifecycle policies and detection rules stay as configured. Bring the relevant context together The HiveSilo audit event: what happened, when and how severe it was, with a hashed reference to who or what was involved. The index or data stream and the ECS fields on the document. Your own saved searches and detection rules for access change. Make the decision The reviewer finds the change in the weekly search and confirms it against an approved request. A useful output A document in your cluster that searches, dashboards and detection rules can use. Keep responsibility clear Your security team owns the review and any rule that runs on the data. HiveSilo supplies the event; it does not create or change rules in Elastic Security. Hold and ask If Elasticsearch rejects the request, for example because the key lacks the index privilege, treat the feed as interrupted until the key or target is corrected. Record the outcome Keep the document under the lifecycle policy you set for that index or data stream. [P719-D01] [P719-D08] [P719-D10] Require control before AI acts. Give the key the least it needs: add documents to one target. Create an API key used only for the HiveSilo feed, with the create_doc privilege on one index or data stream and nothing else. Set an expiration that matches your rotation practice and name an owner for renewal. Agree in advance which ECS category values the events use, and leave a categorization field empty where no published value fits, as ECS advises. 1 Request An AI proposes an action 2 Check Policy and authority 3 Approve Named owner, when required 4 Act Within permitted scope 5 Record Keep the action, outcome and accountable owner traceable. Unclear authority? Hold the action. Resolve with the named, authorized owner before proceeding. Controls apply to actions routed through the configured HiveSilo boundary. Read the governance and escalation requirements Make accountable authorization a condition of putting AI to work. HiveSilo describes an operating layer that combines buyer intelligence, customer-data privacy and governance. Your deployment should establish the responsible owner and permitted scope before an agent can change records, contact buyers or trigger campaigns. HiveSilo documents policy checks before execution, default denial when authorization is unclear, human checkpoints, scoped stop controls and decision receipts. These controls apply to actions routed through its policy boundary. Keep decisions, required approvals and held actions traceable as the workflow progresses, then record the action, outcome and accountable owner. [HS6] [HS7] Who Identify the acting agent or person and name the business owner accountable for this workflow. What Define the action and permitted data categories before execution. Where Specify the approved system, destination and customer custody boundary. How Require an approved execution path, access scope and applicable policy checks. When Set the permitted conditions and approval validity; recheck authority before a held action resumes. Why Record the business purpose and the basis for allowing, denying or holding the action. An edge case should stop the affected action. For the deployment, require unresolved authority, an unapproved destination or an out-of-policy action to remain on hold. A timeout or unanswered approval request must not become permission to proceed. Who gets the question? Agree a named owner and authorized delegate for each workflow. A proposed responsibility model is: sales for buyer outreach and lead handling; marketing for campaign spend and audiences; security or privacy for data-access exceptions; the platform owner for connector or runtime changes. Test the escalation route. If no authorized reviewer is available, keep the action held. Named-owner routing is configured and demonstrated for each deployment. Governance covers actions routed through its configured boundary; external systems remain responsible for actions outside that scope. Make responsibility part of the AI rollout. Use the AI implementation layer to put policy checks, approval checkpoints and decision records around the actions in scope. Your enterprise agreement defines the legal responsibilities and any agreed liability allocation or transfer. [HS7] [HS10] Explore the AI implementation layer · How enterprise agreements govern the engagement Your client list stays yours. These are HiveSilo's own audit and security events, not your visitors or leads. Explore the security architecture Your client records stay with your business under HiveSilo’s published architecture. How your data stays under your control The feed carries HiveSilo's audit and security events for your tenant, with hashed identifiers. It does not carry visitor or lead data. Customer identities stay in the environment you control, and Elasticsearch roles govern who can read the documents. [P719-D01] [P719-D04] [HS3] [HS4] [HS4] Your controlled environment Customer identities stay in your environment Identities and re-identifiable records stay here. Your enclave. Your keys. Only permitted non-PII signals and scores HiveSilo audit and security events, hashed identifiers HiveSilo intelligence Your Elasticsearch index, under your API key No customer identity transfer to HiveSilo. Published architecture. Confirm the data boundary for your deployment. Customer-controlled keys Documented BYOK options cover AWS, Azure and GCP. Review key ownership, revocation and the deployment's access policy with your security team. [HS3] Protected processing The architecture describes confidential computing and trusted execution environments. Request deployment-specific attestation and data-flow evidence for your CISO's review. [HS3] Scoped destinations and actions Agree which systems receive outputs and what actions are authorized. Keep identity handling within the documented customer boundary. [HS2] [HS4] Control through the full relationship Review permitted use, export, retention, deletion and offboarding terms. Customer-controlled keys are one control; they do not establish every contractual exit right. [HS3] [HS4] Each event describes an action in your HiveSilo tenant: what happened, when and how severe it was, with a hashed reference to who or what was involved. Visitor and lead data is not part of this feed. Customer identities stay in the environment you control. Once a document is in your cluster, your Elasticsearch roles and lifecycle settings govern who can read it and for how long. An Elastic review of the connection should confirm the API key, its index privilege and its expiration. [P719-D01] [P719-D04] [HS3] [HS4] Customer identity custody is separate from HiveSilo account, billing and support records. Re-identifiable pseudonymous data is not anonymous. What you could gain. HiveSilo scores buyers on your website. The Elastic connection gives your security team the audit trail of how that system is administered. Explore HiveSilo case studies Contact HiveSilo Select a benefit to explore Pause rotation Buyer scoring Scale winners Less waste Bot protection Find revenue 3,790 of 5,000 · UHNW buyer score 3 , 7 9 0 of 5,000 Illustrative score 4–6× · Reported conversion lift 4 – 6 × Closed-revenue outcomes Up to 31% · Reported ad-spend savings Up to 3 1 % Bot and invalid-traffic filtering 99.9999% · Bot detection 9 9 . 9 9 9 9 % Observed client results 5–21% · Revenue lift from existing data 5 – 2 1 % HiveSilo-reported client results Sharper scoring. Clearer intent. 3,790 of 5,000 · UHNW buyer score Illustrative score Buyer scoring runs on your own website, and Elastic shows your security team who administered it. Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes Bring more sites onto what works while the same Elastic searches cover each one. Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Retire a separate vendor log review by querying HiveSilo audit events in Elastic. Keep evolving your protection. 99.9999% · Bot detection Observed client results Index traffic-protection alerts about bots and invalid traffic where your Elastic detections can read them. Goal, not an achieved result: toward 99.9999999% bot detection as the hive evolves. Observed client results vary. Find revenue in data you already own. 5–21% · Revenue lift from existing data HiveSilo-reported client results Use the audit documents in Elastic to show how the data behind your revenue decisions was accessed and handled. Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary. Measure what matters Define the result. Then require the evidence. Focus on better-directed follow-up, less acquisition waste, protected customer identity custody and accountable AI execution. Agree the baseline, success measures and scope for your business. CEO: a clearer decision about the opportunities that merit attention. CFO: an agreed baseline, evaluation costs and attributable outcomes before any ROI claim. CTO: a demonstrated, permitted connection and a usable handoff into the agreed system. CISO: verified identity custody and pre-action authorization, with tested hold, approval and revocation behavior. Explore HiveSilo’s published outcomes and the measurement context behind them. [HS5] [HS8] [HS9] Make your next conversation count. Bring your Elastic workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise key management & security monitoring · Security, compliance, technology & operations Contact HiveSilo Mention Elastic and your business question. No client records or credentials. A closer look, when you need it. Product scope, a practical workflow and source-backed answers for your team and its research tools. Read fact sheet Structured JSON RSS updates Reviewed November 2026 Contact HiveSilo Elastic connection & briefing scope Agree the deployment address, the key and the target. Your Elastic administrator names the index or data stream, creates an API key limited to adding documents there, and shares the address of your Elasticsearch deployment. HiveSilo stores the key for your tenant and writes only to that target. The connection is available and is activated for each client on request. Public documentation establishes what the Bulk API and ECS support; your Elastic configuration and your agreement with HiveSilo determine the scope that is switched on. When reviewing Elastic with HiveSilo, ask which ECS category values the audit events should carry. [P719-D01] [P719-D04] [HS3] [HS4] [P719-D01] [P719-D03] [P719-D04] [HS10] A useful fit when Most useful where Elastic is the security team's system of record and vendor audit trails are expected in the cluster. Organizations that run Elasticsearch with Kibana or Elastic Security for investigation. Teams with audit or retention obligations that cover software vendors. Teams able to name the index or data stream, the key owner and the ECS mapping for a new source. Consider the fit Your deployment address must be reachable for outbound calls from HiveSilo. Index templates and lifecycle policies for the target are set up by your team. The feed carries audit and security events only. Buyer scores and leads go to your CRM or warehouse, not to Elastic. In your enquiry, name Elastic and the business decision. Please leave out client records, credentials and sensitive samples. Eight questions before your briefing 1. Does HiveSilo connect to Elastic? Yes. The Elastic connection is available and is activated for each client on request. It uses the documented Elasticsearch Bulk API with an API key your administrator creates. [P719-D01] [HS2] 2. What does HiveSilo send to Elastic, and does it read anything back? It sends its own audit and security events for your tenant: administrative and access actions, data-rights requests, and traffic-protection alerts. Each says what happened, when and how severe it was, with a hashed reference to who or what was involved. It is not visitor or lead data. The event layout is shared under agreement during setup. HiveSilo only adds documents. Searching needs the read privilege, which is separate from create_doc and which this connection does not ask for. [P719-D07] [P719-D16] [HS3] 3. Which Elastic products and features are in scope? Elasticsearch receives the documents through the Bulk API, into an index or data stream. Kibana manages the API key and searches the data. Elastic Security can read the events because they carry the ECS fields it requires, and its detection rules can alert on them. Ingest pipelines and data stream lifecycle retention are yours to add. HiveSilo configures none of those; it supplies the events. [P719-D01] [P719-D04] [P719-D10] [P719-D12] [P719-D14] [P719-D15] 4. Which endpoint does it use, and can we test first? POST /_bulk or POST /{index}/_bulk, with a newline delimited JSON body. For a data stream the action is create, which is the only action data streams support. If you put an ingest pipeline in front of the target, Elastic documents a simulate pipeline API and a Kibana test with sample documents, and it suggests validating detection rules before enabling them. [P719-D01] [P719-D12] [P719-D15] 5. What privileges does the API key need? For the create action, Elastic lists the create_doc, create, index or write index privilege on the target. The key is sent as \"Authorization: ApiKey\" with the encoded value. [P719-D01] [P719-D02] 6. Do the events follow the Elastic Common Schema? ECS is the documented field set. Elastic Security requires @timestamp, ecs.version, event.kind, event.category and event.type on all data, and ECS allows vendor fields nested under a proper name. How HiveSilo events map to ECS is agreed at setup. [P719-D06] [P719-D09] [P719-D10] 7. How do we stop the feed? Delete the API key in Kibana, which needs the manage_api_key or manage_own_api_key privilege. You can also set an expiration when the key is created, or ask HiveSilo to switch the connection off. [P719-D03] [P719-D04] 8. Is there a HiveSilo integration package for Elastic? No package or listing is claimed. Elastic publishes integrations through its integrations repository. This connection needs none: it is an API key and the documented Bulk API. [P719-D11] Sources, scope & verification Elasticsearch API: Bulk index or delete documents [P719-D01] POST /_bulk and POST /{index}/_bulk perform multiple actions in one request with a newline delimited JSON (NDJSON) body whose final line ends with a newline; the create action needs the create_doc, create, index or write index privilege; data streams support only the create action; there is no \"correct\" number of actions per request. Reviewed November 2026 Elasticsearch API documentation: Authentication [P719-D02] The API accepts bearer, basic and API key authentication; an API key is sent as \"Authorization: ApiKey\" with the encoded value, and keys come from the /_security/api_key APIs. Reviewed November 2026 Elasticsearch API: Create an API key [P719-D03] POST /_security/api_key creates an API key; by default API keys never expire and an expiration can be set at creation; the call requires the manage_own_api_key cluster privilege. Reviewed November 2026 Elastic Docs: Elasticsearch API keys [P719-D04] API keys are managed in Kibana; using them there needs the manage_security, manage_api_key or manage_own_api_key cluster privilege, and deleting keys needs manage_api_key or manage_own_api_key; a personal key created from the Connection details panel has a default expiration of 90 days. Reviewed November 2026 Elasticsearch Reference: Networking settings [P719-D05] http.max_content_length is the maximum size of an HTTP request body and defaults to 100mb. Reviewed November 2026 Elastic Common Schema (ECS) reference [P719-D06] ECS is an open source specification that defines a common set of fields for storing event data, such as logs and metrics, in Elasticsearch. Reviewed November 2026 Elastic Common Schema: Event fields [P719-D07] Defines the event field set, including event.action (the action captured by the event) and event.outcome (whether the event represents a success or a failure). Reviewed November 2026 Elastic Common Schema: ECS categorization fields [P719-D08] ECS defines four categorization fields: event.kind, event.category, event.type and event.outcome. Events that match no published value should leave the fields empty. Reviewed November 2026 Elastic Common Schema: Custom fields [P719-D09] Custom fields are allowed alongside ECS; nesting custom fields under a proper name, such as a company name, is described as a relatively safe approach. Reviewed November 2026 Elastic Security ECS field reference [P719-D10] Elastic Security requires event data to be normalized to ECS; all data must contain @timestamp, ecs.version, event.kind, event.category and event.type. Reviewed November 2026 Elastic Docs: Publish an integration via Pull Request [P719-D11] A published Elastic integration is a package added to the integrations repository by pull request and released to the package registry. HiveSilo does not claim an Elastic integration package. Reviewed November 2026 Elastic Docs: Elasticsearch ingest pipelines [P719-D12] Ingest pipelines perform transformations on data before indexing through processors that run sequentially; managing them needs the manage_pipeline cluster privilege; Elastic recommends testing a pipeline with sample documents in Kibana or with the simulate pipeline API (POST _ingest/pipeline/_simulate); index.default_pipeline sets a default pipeline. Reviewed November 2026 Elastic Docs: Data streams in Elasticsearch [P719-D13] A data stream is a single named resource over backing indices optimized for append-only time series data such as logs and events; it requires a matching index template, and every document must contain a @timestamp field. Reviewed November 2026 Elastic Docs: Data stream lifecycle in Elasticsearch [P719-D14] Data stream lifecycle manages retention: data is kept at least for the retention time defined and data older than the retention period is deleted automatically later; retention can be configured on the data stream level or on a global level. Reviewed November 2026 Elastic Docs: Detections and alerts [P719-D15] Elastic Security's detection engine evaluates data against detection rules and generates alerts when rule criteria are met; the suggested lifecycle includes validating rule logic against historical data before enabling. Reviewed November 2026 Elasticsearch Reference: Elasticsearch privileges [P719-D16] The create_doc index privilege allows indexing documents and does not grant permission to update or overwrite existing documents; the read index privilege gives read-only access to actions such as search and get. Reviewed November 2026 HiveSilo capability overview [HSF1] Published HiveSilo capabilities relied on here: AI Governance & Control, AI firewall, bot defense and site protection, business insights and oversight, and client-controlled privacy and verification; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. Reviewed November 2026 HiveSilo: industry coverage [HS0] First-party description of buyer intelligence across 12 luxury niches. Reviewed October 2026 HiveSilo: platform [HS1] Published intent, sales-prioritization and traffic-quality capabilities. Reviewed October 2026 HiveSilo: integration scope [HS2] Named destinations, scoped activation and customer-controlled dispatch. Reviewed October 2026 HiveSilo: security architecture [HS3] Documented confidential processing, BYOK and customer control. Reviewed October 2026 HiveSilo: data handling [HS4] Customer identity custody, pseudonymous-data boundaries and separate account records. Reviewed October 2026 HiveSilo: published outcomes [HS5] Existing first-party outcomes material, with client-reported and illustrative descriptions. Reviewed October 2026 HiveSilo: AI agentic governance [HS6] Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts. Reviewed October 2026 HiveSilo: AI implementation layer [HS7] Published combined implementation model for intelligence, confidential processing and AI governance. Reviewed October 2026 HiveSilo: bot-detection results and buyer-score specimen [HS8] The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen. Reviewed October 2026 HiveSilo: owned-data revenue result briefing [HS9] HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows in October 2026. Reviewed October 2026 HiveSilo: enterprise agreements and responsibility [HS10] Signed enterprise agreements govern the engagement and take precedence over website summaries. Reviewed October 2026 Vendor sources describe their own product. The workflows on this page describe a HiveSilo application, scoped to customer permissions, contracts and the selected product edition. HiveSilo’s reported outcomes retain their original measurement context; the illustrative score and future bot-detection goal are identified in the outcomes section. Independent HiveSilo use-case page. Elastic is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. Contact HiveSilo"
}
