Logpoint

Create an outgoing webhook to create incidents on Logpoint triggered by Apono access request events

Logpoint collects real-time data from multiple sources and centralizes it for comprehensive analysis. You can search, analyze, generate reports, detect vulnerabilities, and configure alerts to enhance threat detection capabilities. You can also automate threat response based on specific security incidents.

Prerequisite

  • Logpoint API requires two request parameters:

    • username, which includes a Logpoint username. Your access control for using the APIs is the same as your user roles in the system

    • secret_key, which is the access key to uniquely identify you as an authorized user.

      \

Configure a webhook

Follow these steps to configure a webhook:

  1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

  2. Click Request Webhook.

  3. Enter a unique, alphanumeric, user-friendly Request Webhook Name for identifying this webhook.

  4. Click the Status toggle to Active.

  5. From the Method dropdown menu, select POST.

  6. For the webhook URL, enter https://Logpoint-IP/reopen_incident.

  7. In the Body Template field, construct a JSON body for the webhook payload.

    {
   "username": "<username>",
   "secret_key": "<secret_key>",
   "requestData": {
        "version": "0.1",
        "incident_ids": [
            "5a62bd8cce983de89085429c",
            "5a62bd8cce983de89085429b",
            "5a62bd8cce983de89085429e"
        ]
    }
}

Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.

  1. From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:

    • RequestCreated

    • RequestApproved

    • RequestExpired

    • RequestFailed

    • RequestGranted

    • RequestRejected

  2. Under Filters, define one or several filter from the listed dropdown menus.

Filters empower admins to control the data transmitted via webhooks, minimizing the amount of data third-party tools receive and reducing unnecessary clutter.

Examples:

  • Send only production requests to your admins' Slack channel.

  • Trigger Okta workflows for events from specific integrations or resource types.

  • Open a ticket in Jira or ServiceNow for manually approved requests.

  1. (Optional) In the Timeout in seconds field, enter the duration in seconds to wait before marking the request as failed.

  2. (Optional) Define Response Validators to verify that the response from the webhook meets specified criteria:

    1. Click + Add. A row of settings appears.

    2. Starting with $.data., enter the Json Path of the JSON parameter.

    3. In the Expected Values field, enter a value and press the Enter key on your keyboard.

    4. Repeat step c to add several expected values.

    5. Repeat steps a-d to add multiple response validators.

  3. Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.

For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.

Should your test fail, view these tips to troubleshoot your webhook.

  1. Click Save Webhook.

The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.

Apono access request incident will be created on Logpoint based on the triggers you have selected.

PreviousCortexNextSplunk

Last updated