Install Guide
The AIM Starfort app inspects text for personal data with the AIM Intelligence Starfort Guard API. It works as a guardrail that checks what AI agents send to their models and masks or blocks it, and it can also be used directly from a screen and from query commands. Installing the app alone is not enough; the following must be in place as well.
- A Starfort API key issued by AIM Intelligence (starts with
sf_). - HTTPS access from the Logpresso server to the Starfort Guard API endpoint. If there is no direct route, set an HTTP proxy.
- To use it as the AI agent guardrail, the AI Assistant or Agentic SOC app 1.13 or later. The guardrail test screen and the query commands work without an AI agent app.
Follow the steps in order.
1. Install the app
Install AIM Starfort from the App Store.
Once installed, Guardrail Test appears in the left menu and AIM Starfort is added to the connect profile types.
2. Register a connect profile
Add a connect profile of type AIM Starfort.
| Item | Required | Description |
|---|---|---|
| Endpoint | Yes | Base URL of the Starfort Guard API. Defaults to https://bastion-guardian-api.starfort.io; /v1/guard/api is appended when calling |
| API Key | Yes | Value sent in the X-Starfort-Guard-Api-Key header. Stored encrypted |
| Connect Timeout | No | In seconds, 1 to 300. 10 by default |
| Read Timeout | No | In seconds, 1 to 300. 30 by default |
| HTTP Proxy | No | IP:port |
After saving, run Test Connection. It sends a short sentence with no personal data and checks that HTTP 200 and a verdict come back. On failure the error code and Starfort's X-Request-ID are shown.
3. Verify the installation
Open the Guardrail Test menu and check that inspection actually works.
- Select the connect profile
- Click the sample button Mobile number (MASK)
- Click Inspect
- The verdict is MASK and
processed_contentshows the number with its middle digits hidden, such as010-****-5678
When using it as the AI agent guardrail, open the Guardrails tab of the AI Agents menu and click the gear at the top right. If AIM Starfort is shown as Ready with the connect profile in use, the guardrail is on.
4. Moving to the on-premises environment
After testing, when the app is moved into the on-premises environment, change the Endpoint and API Key of the connect profile to the on-premises values. Verdict handling stays the same. Run Test Connection and the checks in step 3 again after the change.
Troubleshooting
| Symptom | Cause | Action |
|---|---|---|
217400 connect profile not found | No AIM Starfort connect profile | Register one as in step 2 |
217401 API key not set | The API key of the profile is empty | Enter the API key; make sure it has no surrounding spaces or line breaks |
217402 invalid endpoint | The URL is not http or https | Enter an address starting with https:// |
217404 invalid proxy | HTTP proxy is not IP:port | e.g. 10.0.0.1:3128 |
217411 HTTP 401 (API_KEY_INVALID) | Wrong API key, or its validity period has ended | Check the key and its period with AIM Intelligence |
217412 HTTP 403 | Access is restricted | Contact AIM Intelligence |
217414 HTTP 5xx | The inspection engine could not reach a verdict | Retry later; if it persists, contact AIM Intelligence with the X-Request-ID |
217415 connection failed or timed out | Network blocked or proxy not set | Allow HTTPS to the endpoint on the firewall, or set an HTTP proxy |
| Guardrail status is Not ready | No AIM Starfort connect profile | Register one as in step 2 |
| AIM Starfort is missing from the guardrail status | The AI agent app is older than 1.13 | Update the AI agent app to 1.13 or later |
Once installed, see the User Guide for how to use the app.