Leen

Collect findings from the security tools you connect through Leen, and promote them to risks or evidence.

Leen (Leen.dev, a unified security API) sits between Aegis and your scanning tools. You give Aegis one Leen API key for the organisation, then add one connection per tool — Tenable, Rapid7 InsightVM, Semgrep, SecurityScorecard, Wiz Code, Aikido, GitLab or GitHub Advanced Security. Each connection pulls that tool's findings (the vulnerabilities, code issues and scores it reports) into a findings list in Aegis, where a person decides which ones become a risk or evidence.

At a glance

Direction Into Aegis.
What it brings in Findings from each tool connected in your Leen account (one Aegis connection per tool).
Where it lands The Leen findings list. Lower-severity findings become evidence drafts; critical and high findings wait for a person to promote them to a risk (or to evidence), because a risk needs a category, impact and likelihood.
Credentials and permissions A Leen API key, checked with Leen before it is saved, plus the credentials each tool needs (for example an access key and secret key for Tenable, or a personal access token for GitLab).
Owner of imported records The person who saved the Leen API key becomes the default owner of evidence created during a sync. Without one, no evidence is created. Findings you promote by hand are owned by you.
When it runs On a schedule under Sync Settings (see Connectors), or on demand per connection with Sync now.
Where the data goes Aegis calls Leen in its EU region (Frankfurt) only.
Set it up /connectors/leen, by a Manager or Admin, on a plan that includes the connector.

Who uses it

Admin and Manager can do everything on these pages: save the API key, add, sync, test and delete connections, and promote findings. Contributor and Viewer users are sent away from /connectors/leen and its sub-pages.

The pages also need the Leen connector switched on for your organisation and a licence that includes the Leen integration. If either is missing, the address shows a not-found page instead of an empty screen.

What's on this screen

No screenshot of the Leen pages is included in this chapter. Open Leen from the Connectors catalogue. The page is headed Leen — Unified Security API, with the subtitle “Federate vulnerability, AppSec, and TPRM data through Leen.dev” and a breadcrumb back to Connectors. What follows depends on whether the API key has been saved.

Save the Leen API key

  1. Open /connectors/leen. The “Leen is not yet configured for this workspace” panel explains that the key is encrypted at rest and never logged.
  2. Paste the key into Leen API key. The field hides what you type. A key shorter than 16 characters is refused on the page with “Leen API key must be at least 16 characters”.
  3. Select Save API key. Aegis checks the key with Leen first. If Leen accepts it, the page reloads with the empty connections list. If Leen rejects it, you see “Leen rejected this API key — double-check it and try again”. If Leen cannot be reached, the message says so and that your key has not been saved, so you can try again later without changing it.

Add a connection

Add a connection opens /connectors/leen/new, headed Add Leen connection. Three numbered stages run across the top: Choose a vendor, Enter credentials and Review & create.

  1. Under Choose a vendor, select one of the eight tool cards. Each card names the tool and what it brings in, such as “Static analysis findings from Semgrep” or “Third-party risk scores from SecurityScorecard”. Selecting a card moves you to the credentials stage.
  2. Under Enter credentials, give an optional Display name (the label shown in Aegis; the tool's name is used if you leave it blank) and fill in the tool's own fields. These differ per tool: Rapid7 InsightVM asks for a Base URL, Username and Password; Wiz Code and Aikido ask for a Client ID and Client secret; GitHub Advanced Security accepts either a personal access token or GitHub App details. Fields marked (optional) may stay empty.
  3. Select Next. A required field left empty stops you with “… is required”, naming the field. Otherwise the review stage shows the vendor, the display name and each credential you entered, masked as dots.
  4. Select Create connection (it reads Creating... while it works). Aegis registers the connection with Leen. On success you return to the Leen page with the new row in the table; if Leen refuses the credentials you see “Leen rejected the connection — check the credentials and try again”. Back on either later stage returns you one stage.

Check, sync and test a connection

Select a vendor name in the table to open the connection's page. It is headed with the display name (or the tool's name) and the tool's description.

  1. Read the Connection status panel. It shows Status and Last sync. After a failed sync or test, a Last error line reads “The last sync or connection test failed. Check the audit log for details.”, sometimes with an Error code from Leen beneath it.
  2. Select Sync now (it reads Syncing... while it runs). When it finishes, a message reports the counts in the form “Synced — … imported, … updated, … promoted” and the page refreshes with the new findings.
  3. Select Test connection to check the credentials without importing anything. A working connection reports “Connection test successful”.

Sync now on a row of the connections table does the same as the button here, without opening the page.

Review and promote findings

The Recent findings panel lists the 20 findings most recently imported for this connection, under Severity, Title, State, Updated and Actions. Severity is a labelled badge — Critical, High, Medium, Low, Informational or Unknown. State is Open, Closed, Reopened, Ignored, Deleted at source or Unknown. Before the first sync the panel reads “No findings imported yet.”; if the list cannot be loaded it reads “Findings could not be loaded. Try again or run a sync.”

  1. Select Promote to Evidence on a row. Aegis creates an evidence draft owned by you, and the button changes to Promoted to Evidence and can no longer be selected. A finding already promoted by a sync shows Promoted to Evidence from the start.
  2. Select Promote to Risk on a row. A Promote finding dialog opens, explaining that a risk needs a category, impact and likelihood and that the action is logged in the audit trail.
  3. Choose a Risk category, keep or change the Risk title (it defaults to the finding title), and set Impact (1–5) and Likelihood (1–5), which both start at 3.
  4. Select Create Risk. The dialog closes, a confirmation appears, and the row shows Promoted to Risk. Cancel closes the dialog without creating anything.
No risk categories, no risk

If your organisation has no risk categories yet, the dialog says “No risk categories exist yet, so a risk cannot be created.” and Create Risk stays unavailable. People allowed to create categories get a Manage risk categories link; everyone else is asked to contact an administrator. See Risks.

Delete a connection

  1. Select Delete connection, on the connection's page or on its row in the table. A dialog asks “Delete this Leen connection?” and explains that the connection stops syncing and leaves the list, and that risks and evidence already promoted from its findings are kept.
  2. Confirm. You see “Connection deleted” and the row disappears; from the connection's page you return to the Leen list.

How a sync treats findings

Good to know

Where this connects

Promoted items are worked in Risks and Evidence. Schedules and the catalogue of other connectors are in Connectors.