IT that keeps manuscripts unleaked, royalties on course, your masthead yours.IT that keeps manuscriptsunleakedroyaltiesoncourseyourmastheadyours
IT and security for publishers whose inboxes, payment runs and publishing tools are trusted by authors, readers and advertisers.
Publishing IT
Your next big title is sitting in an inbox
Publishing runs on trust between authors, agents, editors, printers and readers, and most of that trust travels by email. Manuscripts, contracts, royalty statements and print files move back and forth every day. That's exactly what attackers imitate. Here's what a publisher depends on, how impersonation and account takeover actually play out, and what we put in place.
01 · The pressure
Embargoes, print dates and payment runs
Editors trade drafts with agents and authors, production sends InDesign files to typesetters and printers, rights teams negotiate translations, and finance runs advances and royalty payments. Digital teams publish through WordPress VIP, Arc XP or another CMS, and subscriptions run through Piano or a similar platform. Embargoes and print dates are fixed. A leaked manuscript, a hijacked royalty payment or a fake story published on your site damages relationships that took years to build.
- Drafts move between agents, authors and editors
- Royalty and advance payments go out on schedule
- One CMS login can publish under your name
Adobe InDesignWoodWing StudioWordPress VIPArc XPPianoMicrosoft 365
02 · How it breaks
Lookalike agents and redirected royalties
Attackers register domains a letter off from a real agency or imprint and email editors asking for the latest draft. Others pose as an author asking finance to update bank details before a royalty run. A freelance copyeditor's account is compromised and used to reach shared folders. A CMS editor reuses a password, and someone posts a fake article or injects spam links. Subscriber databases get exported by an over-permissioned marketing tool integration.
- Lookalike domains requesting unpublished drafts
- Fake author requests to change bank details
- Hijacked CMS logins posting fake content
Adobe InDesignWoodWing StudioWordPress VIPArc XPPianoMicrosoft 365
03 · What we change
Verified senders, guarded files, locked CMS
We add impersonation and lookalike-domain filtering to editorial mail and flag external senders clearly. Manuscripts move through access-controlled shared folders with expiring links instead of attachments. Finance confirms any author or vendor bank change by phone using details already on file. CMS and subscription platforms get SSO or MFA and role limits, so contributors can draft but not publish. We review third-party integrations with subscriber data and remove ones that aren't needed.
- Lookalike-domain filtering on editorial mail
- Expiring, access-controlled manuscript sharing
- Callback rule for author and vendor bank changes
Adobe InDesignWoodWing StudioWordPress VIPArc XPPianoMicrosoft 365
04 · The after
Authors and agents trust you with the next book
Editors still move fast, but requests for drafts from unfamiliar addresses get caught and questioned. Royalty runs go to the right accounts. Agents asking how their client's manuscript will be handled get a clear answer. The digital team publishes without worrying that a stolen password will put a fake story on the homepage. And when an author leaves or a freelancer finishes, their access to drafts ends with them.
- Suspicious draft requests flagged on arrival
- Royalties land in the right accounts
- Freelancer access ends with the project
Adobe InDesignWoodWing StudioWordPress VIPArc XPPianoMicrosoft 365