IT that keeps sources protected, the CMS honest, the site up at 2 a.m..IT that keeps sourcesprotectedtheCMShonestthesiteupat2a.m.
Security and support for newsrooms whose reporters, sources and readers all depend on systems staying trustworthy.
Newsroom IT
Someone wants your reporter's inbox more than you do
A newsroom is a small business with an outsized target on it. Investigations make powerful people unhappy, breaking news brings traffic spikes and hostile attention, and the CMS can publish to thousands of readers in seconds. Here's what a news day depends on, how outlets actually get hit, and what we put around them.
01 · The pressure
Deadlines, tips and traffic spikes
Reporters file from city hall, courthouses and their cars, editors publish through Newspack, BLOX or Brightspot, and the homepage changes every hour. Tips come in through email, Signal and a SecureDrop instance if you run one. The audience team sends newsletters to subscribers whose payment details sit with your paywall platform. On a big night, traffic jumps many times over. If the CMS goes down or gets abused, you lose the story, the audience and some of the trust you built.
- Constant publishing from anywhere
- Confidential tips and source communications
- Traffic that spikes with every big story
NewspackBLOX CMSBrightspotNavigaSecureDropSignalPianoGoogle Workspace
02 · How it breaks
Targeted phishing and a borrowed CMS login
An investigative reporter gets a convincing interview request with a malicious attachment from someone connected to their story. A freelancer's reused password opens their CMS account, and a fake article goes live overnight. Reporter laptops with source notes and recordings travel without encryption. A traffic flood knocks the site offline the night of an election. And the shared newsroom social account, with its password on a sticky note, posts something nobody on staff wrote.
- Spear phishing aimed at investigative staff
- Stolen contributor logins publishing fakes
- Floods that knock the site offline
NewspackBLOX CMSBrightspotNavigaSecureDropSignalPianoGoogle Workspace
03 · What we change
Hardened reporters, a locked CMS and a site behind a shield
Reporters and editors get security keys, password managers and encrypted, managed laptops, plus a briefing on targeted phishing and device seizure at borders or protests. CMS access moves behind SSO and MFA, with publishing rights limited by role and logs reviewed. Freelancers get contributor roles that can't publish directly. We put your site behind a CDN with DDoS protection and caching tuned for breaking news, set up and maintain secure tip channels and lock down newsroom social accounts with shared admin roles.
- Security keys and encrypted reporter laptops
- Role-limited CMS publishing with SSO
- CDN and DDoS protection for big nights
NewspackBLOX CMSBrightspotNavigaSecureDropSignalPianoGoogle Workspace
04 · The after
Your masthead means what it says
Sources can reach you through channels you understand and maintain. An investigative team can work a sensitive story without wondering whether a reporter's mailbox is already compromised. Election night brings a traffic spike your site absorbs. If a fake article ever appears, logs show exactly which account published it and when. And your editor spends the night on the story, not on the phone with a hosting company.
- Tip channels sources can rely on
- Logs that trace every published change
- Big nights that the site actually survives
NewspackBLOX CMSBrightspotNavigaSecureDropSignalPianoGoogle Workspace