Why This Journalist Profile Matters
Most security writers learn the beat by reading other security writers. Fahmida Y. Rashid came at it from the other side of the desk. Before her byline ever ran on a breach story, she had been the person carrying the pager: an IT administrator, a software developer, a data analyst. That ordering matters. It is the difference between describing a SQL injection from the documentation and describing it from the memory of a Friday night you spent cleaning up one.
This is a journalist profile of someone who spent roughly two decades covering enterprise technology and security, and who now sits in the seat that decides what Dark Reading publishes at all: editor-in-chief. For readers who think cybersecurity journalism is just a treadmill of CVE numbers, her arc is the better story. It is a working model of how domain expertise turns into editorial judgment.
The Practitioner Before the Journalist
Here is the part most profiles skip. Rashid was not a journalism-school graduate who happened to land a tech beat. She spent years inside the technology she would later write about. As an IT administrator she owned infrastructure problems. As a developer she wrote code that had to ship. As a data analyst she lived in the gap between what a dashboard promised and what the logs actually said.
That résumé is rare on the security desk, and it shows in what she chose to write. Security coverage splits into two camps: press-release regurgitation, and stuff that survives contact with a real sysadmin. The background puts her firmly in the second camp. When she later wrote the explainer on the nine types of phishing attacks, you could read the practitioner's instinct in how each category was framed — not by attack code, but by how the victim actually gets fooled.
A working editor who has done the job asks different questions. Whose alert was ignored? Who was understaffed? What would a competent team have done differently at 2 a.m.? Those questions are what separate analysis from announcement, and they trace straight back to the years before the first freelance invoice.
A Career Built Across the Enterprise Beat
By the time the Dark Reading chair came into view, her byline had already done a lap through the serious enterprise-tech outlets. Her published body of work spans CSO, InfoWorld, eWeek, PC Magazine, and CRN — not a random list. Those are the titles that IT leaders, security practitioners, and CIOs actually read when they are making buying and budget decisions. That is the B2B security market in miniature, and she had covered most of its newsrooms.
The coverage itself reads like a field guide to the modern threat cycle. At InfoWorld she took on the WannaCry ransomware outbreak and framed it the way it should have been framed at the time: as a failure of slow patching, not as some irresistible act of cyber weather. She profiled the Shadow Brokers as the source of the stolen NSA hacking tools behind the attack, and connected the May 2017 outbreak back to a Windows 7 machine still running in places like Britain's National Health Service. She wrote about Apple's surprise patch for the XP-era EternalBlue bug in 2018. She covered the Panama Papers leak and the FBI's fight over iPhone encryption. She walked through the SolarWinds supply-chain compromise and explained why a software update could become a backdoor. And she spent a long stretch tracking NotPetya — an attack that hit Ukraine first and then the global shipping and logistics chain behind Maersk and FedEx, on the very day the country was being hit by another malware attack.
Read in sequence, that is a reporter who treats every incident as a systems story, not a horror story. The patches that didn't land. The updates that got trusted too easily. The geographic blast radius that globalization hides until it doesn't.
The Line Between Boring and Important
There is a recurring theme in her work that a journalist profile would miss if it only counted breach headlines. Security is boring, and that is the point. "The problem is that most users don't really care about security," she wrote of the Equifax breach, "unless it directly affects them. And for most people, it doesn't directly affect them unless they lose money or their Social Security number gets stolen. Then they get mad."
That observation is the whole editorial problem of B2B security journalism in one sentence. The material that matters most — patch cycles, supply-chain hygiene, third-party access — is the least photogenic stuff in the business. A good editor makes it readable without making it false. She leaned on that principle across the wire: the lesson of Equifax, in her telling, was that "the companies responsible for collecting and storing our personal data aren't doing enough to protect it," and that "it's time for Congress to act."
Her byline tagline, "I, for one, welcome our new computer overlords," is the kind of dry line you leave in the boilerplate because the beat would be unbearable without it. The humor is also, quietly, a credibility signal. People who've actually worked the infrastructure tend to joke like that.
As Editor-in-Chief: From Byline to Blueprint
Dark Reading is one of the defining names in cybersecurity journalism, and as editor-in-chief Rashid now leads its editorial strategy — steering what a security audience reads and argues about, rather than filing the stories herself. The outlet itself has run for more than two decades as the industry's water cooler, and handing that to a practitioner-turned-reporter is a deliberate signal about the kind of coverage the newsroom wants.
The pattern across this whole journalist profile is worth naming plainly. The people who end up setting editorial standards in security are usually the ones who did the job first, wrote about it for twenty years across every enterprise title that mattered, and earned the right to decide what counts as real analysis. A developer who can smell a bad dependency, an admin who knows which patch always gets deferred — that person, made editor, bends a whole newsroom toward the unglamorous questions that actually move risk. The byline changes. The instinct to open the logs stays.
Sources
- Dark Reading — Author page
- CSO Online — Fahmida Rashid
- InfoWorld — Fahmida Rashid
