---
title: "Logging"
slug: "fortanix-users-guide-logging-1"
updated: 2026-06-26T16:26:09Z
published: 2026-06-26T16:26:09Z
canonical: "support.fortanix.com/fortanix-users-guide-logging-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.fortanix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Logging

## 1.0 Introduction

This article describes how to integrate **Fortanix Confidential Computing Manager (CCM)** with **External logging systems**.

Fortanix CCM automatically maintains an internal audit log of system operations from different applications and services, and actions related to accounts, users, and sessions.

The following events are logged:

- App Created
- App Updated
- App Updated Failed
- App Deleted
- App Certificate Downloaded
- App Creation Failed
- Node Enrolled
- Node Attested
- Node Attestation Failed
- Node Enrollment Failed
- Node Deactivated
- Node Certificate Downloaded
- Approve Domain
- Decline Domain
- Approve Image
- Decline Image
- Create Image
- Delete Image
- Image Conversion Succeeded
- Image Conversion Failed
- Certificate Requested by Application
- Create Registry
- Delete Registry
- Update Registry
- Node Reconnected
- Node Disconnected
- Configuration Creation

You can configure Fortanix CCM to send these audit log entries to an external logging system. This article explains how to send Fortanix CCM audit logs to the following external logging systems:

- Splunk
- Azure Log Analytics
- Syslog Server

## 2.0 Audit Logging in Fortanix CCM

> [!NOTE]
> NOTE
> 
> Only an Account Administrator in Fortanix CCM can configure integrations with external logging systems.

### 2.1 Log Management

Fortanix CCM supports integration with the following external logging systems:

- Splunk
- Azure Log Analytics
- Syslog

> [!NOTE]
> NOTE
> 
> Only an **Account Administrator** in Fortanix CCM can configure integrations with external logging systems.

To configure a logging integration, in the Fortanix CCM user interface left navigation panel, click **SETTINGS**, and then click **LOG MANAGEMENT**.

You can configure more than one logging integration at the same time. When multiple integrations are configured, Fortanix CCM sends logs to all configured logging integrations.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (3278).png)

**Figure 1: Log Management**

### 2.2 Sending Audit Logs to Splunk

You can configure Fortanix CCM to send audit log entries to a Splunk server using the [HTTP Event Collector](http://dev.splunk.com/view/event-collector/SP-CAAAE6M) (HEC).

Perform the following steps to configure logging events to Splunk:

1. In the CCM UI left navigation panel, click the **Settings** → **Log Management** menu item.
2. In the **Custom Log Management Integrations** section, click **ADD INTEGRATION** for Splunk.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (3279).png)

**Figure 2: Add Splunk Integration**
3. On the **Splunk Log Management Integration** form:
  1. Enter the IP Address or the hostname of your Splunk server.
    1. Select **Enable HTTPS** to communicate with the Splunk server over HTTPS (recommended) and also select the **Enable SSL** check box in the Splunk Global Settings. *Refer to* [*Section 3.0: Appendix*](/v1/docs/fortanix-users-guide-logging-1#30-appendix) *for the screenshot.*

> [!NOTE]
> NOTE
> 
> If you are using an HTTP connection, then clear the **Enable HTTPS** check box in the Fortanix CCM **Log Management** screen for Splunk and also clear the **Enable SSL** check box in the Splunk Global Settings. *Refer to* [*Section 3.0: Appendix*](/v1/docs/fortanix-users-guide-logging-1#30-appendix) *for the screenshot*.

Depending on the type of TLS certificate the Splunk server is using:
    2. Select **Global Root CAs** if you are using a certificate that is signed by a well-known public CA.
    3. Select **Custom CA Certificate**, if you as an enterprise want to self-sign the certificate using your own internal CA. To do this, upload the CA certificate using **UPLOAD A FILE**. When Fortanix CCM as a client connects to the Splunk server and is presented the server’s certificate, it will be able to validate it using the enrolled custom CA Certificate. To generate the CA certificate, run the following command:

```bash
openssl s_client -connect <endpoint/ipaddress>:port -showcerts
```

Where,
      - `ipaddress`: This is the IP address of the Splunk server.
      - `port`: This is the value of the **Management port**, under **Server settings->General settings** in the Splunk Server. *Refer to* [*Section 3.0: Appendix*](/v1/docs/fortanix-users-guide-logging-1#30-appendix) *for the screenshot.*
    4. In case the Custom CA Certificate has a Common Name (CN) that does not match with the server on which Splunk is deployed, clear the **Validate Hostname** check box which prompts Fortanix CCM to ignore the hostname of the Splunk deployment instance. Only the certificate chain will be validated in this case.
  2. The default **Port** number is **80**. If you are running on a different port, add the applicable port number. If you enable HTTPS in *Step a*, then the default port number is `443`.
  3. Add the name of the Splunk index in the **Index** field to submit events. The index value should be the same as the index in Splunk. *Refer to* [*Section 3.0: Appendix*](/v1/docs/fortanix-users-guide-logging-1#30-appendix) *for the screenshot*. When you push the logs to Splunk, you need to push it to a specific index. This value is sent to the Splunk server and can be set to whatever you like. This will allow distinguishing logs from different sources. For example, the logs from Fortanix CCM can be pushed to the Index source name `fortanix_cloud`.
  4. Enter a valid **Authentication token** to authenticate to the HTTP Event Collector of your Splunk instance. The Authentication token will authenticate Fortanix CCM as a client to Splunk and allow it to push the events to Splunk. *For more information about generating HEC authentication tokens, refer to the Splunk documentation.*

> [!NOTE]
> NOTE
> 
> For security reasons, the authentication token is not displayed in the interface when editing an existing configuration.
4. Click **SAVE** to save the Splunk integration.

![edit-splunk-1.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/21619642112788.png)

**Figure 3: Splunk Log Management Integration Form**

### 2.3 Sending Audit Logs to Azure Log Analytics

You can configure Fortanix CCM to send audit log entries to Azure Log Analytics in the Azure Portal to write log queries and interactively analyze the Fortanix CCM log data.

Perform the following steps to configure logging events to Azure Log Analytics:

1. In the CCM UI left navigation panel, click the **Settings** → **Log Management** menu item.
2. In the **Custom Log Management Integrations** section, click **ADD INTEGRATION** for Azure Log Analytics.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (3279) - Copy.png)

**Figure 4: Add Azure Log Analytics Integration**
3. On the **Azure Log Management Integration** form:
  1. Enter the **Workspace ID** which is the Log Analytics workspace in the Azure portal. It is a GUID to identify the specific log analytics workspace in the Azure cloud. *For more information to create a log-analytics workspace, refer to* [*Create a Log Analytics workspace*](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/quick-create-workspace)*.* To get the Workspace ID after you create a log-analytics workspace:
    1. In the log analytics workspace, click the **Agents management** tab to see the **Workspace ID**.

![AzureLog1.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/4405381056148.png)

**Figure 5: Workspace ID**
  2. The **Custom Log Type** is set to “`fortanix_audit_v1_CL`” for all event logs published to Azure Log collector from Fortanix services. This field is set in `HTTP POST` request header of all the logs published to the Azure log collector and therefore it is used to query logs from Fortanix services in Azure Log Analytics Workspace. *For more information, refer to* [*Use queries in Log Analytics*](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/queries)*.*

![AzureLog3.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/4405386941716.png)

**Figure 6: CCM Event Log Query**
  3. Click **ADD PRIMARY SHARED KEY** to add a shared key. Any request to the Azure Monitor HTTP Data Collector API must include an authorization header. Each event log posted to Azure log analytics workspace from the logging service is authenticated by the log monitor service in Azure by validating the request and checking whether it is signed with either the primary or the secondary key for the workspace that is making the request. To get the Primary Shared Key:
    1. In the log analytics workspace, click the **Agents management** menu item to see the **Primary key**. The Primary key of the Log Analytics workspace is referred to as `shared_key`.

![AzureLog2.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/4405381132820.png)

**Figure 7: Primary Shared Key**
4. Click **SAVE** to save the Azure Log Analytics integration.

![edit-azure-1.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/21619642123540.png)

**Figure 8: Configure Azure Log Analytics**

![AzureLog13.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/4405381173524.png)

**Figure 9: Add Primary Shared Key**

> [!NOTE]
> **NOTE**
> 
> For security reasons, the Primary Shared Key is not displayed in the interface when editing an existing shared key.

#### 2.3.1 References

- Create log-analytics workspace: [https://docs.microsoft.com/en-us/azure/azure-monitor/logs/quick-create-workspace](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/quick-create-workspace). *In the URL refer to the section:* ***Create a workspace***.
- Create log-analytics workspace using CLI - [https://docs.microsoft.com/en-us/azure/azure-monitor/logs/quick-create-workspace-cli](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/quick-create-workspace-cli). *In the URL refer to the sections:* ***Prerequisites*** *and* ***Create a workspace***.
- Monitoring logs: [https://docs.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-overview](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-overview).
- Querying logs: [https://docs.microsoft.com/en-us/azure/azure-monitor/logs/queries](https://docs.microsoft.com/en-us/azure/azure-monitor/logs/queries).

### 2.4 Sending Audit Logs to Syslog

You can configure Fortanix CCM to send audit log entries to the Syslog server.

Perform the following steps to configure logging events to a Syslog server:

1. In the CCM UI left navigation panel, click the **Settings** → **Log Management** menu item.
2. In the **Custom Log Management Integrations** section, click **ADD INTEGRATION** for Syslog.
3. On the **Syslog Log Management Integration** form:
  1. Enter the Hostname or IP address of your Syslog server.
  2. You can communicate with a Syslog server either over a non-secure connection or a secure connection using TLS. Depending on the type of TLS certificate that the Syslog server is using,
    1. Select **Global Root CAs**, if you are using a certificate that is signed by a well-known public CA.
    2. Select **Custom CA Certificate**, if you as an enterprise want to self-sign the certificate using your own internal CA. To do this, upload the CA certificate using **UPLOAD A FILE**. When Fortanix CCM as a client connects to the Syslog server and is presented with the server’s certificate, it will be able to validate it using the enrolled custom CA Certificate
  3. The default **Port** number is TCP `514` at which the server must listen for Syslog messages. If you are running on a different port, change to the applicable port number.
  4. When you log an event in Syslog, you can choose to log it in different facilities. This allows you to filter your log for a specific facility. The facilities appearing in the **Facility** list are well-defined facilities in the Syslog protocol. For example, **User**, **Local0**, **Local1**, and so on. You can configure the Fortanix CCM system to use the Local0 facility for instance. This will help in filtering logs from a particular appliance using a facility.
4. Click **SAVE** to save the Syslog integration.
  1. ![edit-syslog-1.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/21619637787924.png)

**Figure 10: Syslog Integration Form**

## 3.0 Appendix

Following are the Splunk Server screenshots:

- If you are using an HTTPS connection, then select the **Enable SSL** check box below in the Global Settings.

![AzureLog11.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/4405381494292.png)

**Figure 11: Enable SSL**
- Port number on the Splunk server used for generating Custom CA Certificate.

![Sp2.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/20142143943444.png)

**Figure 12: Management Port Number**
- The index value in the Fortanix CCM Splunk Log Management Integration form should be the same as the Default Index value.

![AzureLog12.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/4405387174548.png)

**Figure 13: Index Value of the Splunk Server**

## Related

- [Command-Line Interface (CLI) for Fortanix DSM (sdkms-cli)](/fortanix-dsm-clients-command-line-interface-cli.md)
- [Bringing EDP Rust Apps to Confidential Computing Manager](/bringing-edp-rust-apps-to-fortanix-ccm.md)
- [Troubleshooting](/fortanix-ccm-troubleshooting.md)
- [Usage Metrics](/fortanix-dsm-usage-metrics.md)