Current + Inky integration
Inky sends its phishing catches and user reports to Current, mapped to each customer by domain, for company pages, alerts and business reviews.
Inky has no API to read, so the connection runs the other way: Inky's Custom SIEM Feed posts each email-security event to an address Current gives you. Phishing catches and user reports then show on each customer's company page, in business reviews, and as an alert when they spike.
Set it up in two steps
- In Current, a tenant admin enables the Inky receiver and copies the feed address it shows.
- In Inky, paste that address into the Custom SIEM Feed. The card reads Awaiting feed until the first event arrives, then Receiving.
What Current keeps
Threat signals only: the event type and verdict, a threat level and category, when it happened, and the sender and recipient domains. Email bodies, subject contents, HTML and attachments are removed as each event arrives, before anything is written. Events are kept for 90 days.
Mapping to customers
Each event's recipient domain decides its company: a domain that matches exactly one company's website links automatically, and anything else is stored unmapped. If the feed address is ever exposed, an admin makes a new one and the old one stops working at once.