Docs / Data sources / Security Journey

Security Journey

Business software

Built when you ask for it

Sync Security Journey learner and training progress data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Security Journey connector syncs your security awareness training data into analytics-ready tables in your data warehouse. Pull learners, training progress, and scores from the Security Journey Reporting API, with Ingest handling auth, pagination, and retries so the tables stay current. This is a read-only Reporting API covering learner and training-progress data only, not a general platform API.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Learners
  • Training progress
  • Scores

How it gets built

  1. Choose Security Journey when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Security Journey's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Security Journey itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key (Bearer token, admin-generated). An Admin generates the key under Admin > Connections > Reporting API > "Create Reporting API Key".

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Security Journey connector?
Not as a finished connector yet. Ingest builds it from Security Journey's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Security Journey data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Security Journey API documentation: https://help.securityjourney.com/security-journey-api-v3

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Security Journey