Skip to content

Integrations

Connect Insider Threat Case Management to your systems

Each integration Insider Threat Case Management supports: what flows, how fields map, and the steps to set it up.

Applies to Insider Threat Case Management as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 4 min readReport a problem
On this page
  1. User activity monitoring
  2. Steps to set it up
  3. Network and system logs
  4. Steps to set it up
  5. Human resources
  6. Steps to set it up
  7. Personnel security
  8. Steps to set it up
  9. Physical access
  10. Steps to set it up
  11. Case and referral channels
  12. Steps to set it up
  13. Sign-in
  14. Steps to set it up
  15. Using the Work API

How Insider Threat Case Management connects to your other systems. Every connection is confirmed during discovery and specified in the design before it is built.

User activity monitoring

Concerns your own monitoring tool raises can be sent as Referral records through the Work API by your team, with the detection rule and contributing factors. No activity data is collected.

  • What flows: In: referrals, with the rule and factors the tool gave.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Network and system logs

Not connected: what your log or SIEM team reports reaches the hub as a referral, entered by staff or sent through the Work API.

  • What flows: In: referrals, not log events.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Human resources

Role, department, supervisor and departure notices entered on a case by an analyst, with the HR reference, once a review is cleared.

  • What flows: In: context entered by staff with its source reference.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Personnel security

Clearance and access status entered by an analyst from your personnel security records, such as Moraph's Personnel Security Clearance Tracker, once a review is cleared.

  • What flows: In: eligibility and access status entered by staff. Out: nothing is sent.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Physical access

Badge records an analyst checks in your access control system can be entered on a case as context, with the reference.

  • What flows: In: physical access context entered by staff.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Case and referral channels

Printable referral packages for counterintelligence, law enforcement or the inspector general, delivered by staff through the channel your procedures require.

  • What flows: Out: approved referral packages. In: receipt and outcome, recorded by hub staff.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Sign-in

Hub staff sign in with their Moraph account, using email and password and, optionally, two-step verification. Sign-in through your own identity provider (SAML or OpenID Connect) is not offered.

  • What flows: None: accounts are kept in Moraph
  • Mapping: Agreed in the integration design.

Steps to set it up

  1. Agree the scope of the connection with Moraph during design.

  2. Provide access to the system being connected.

  3. Test the connection in a non-production environment before go-live.

Using the Work API

Systems that aren't covered above can read and write Insider Threat Case Management records through the Sign in to read Work API. For example, to create a referral:

http
POST https://apps.moraph.com/api/v1/records
Authorization: Bearer mrph_…
Content-Type: application/json
Idempotency-Key: 7f3c2a90-example

{ "type": "referral", "title": "Example title", "fields": { "received_on": "…" } }

Field keys are listed in the Sign in to read workspace reference. Request formats, paging and errors are in the Sign in to read Work API reference.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.