About Departmentofinternetsecurity

Departmentofinternetsecurity exists because most security advice is written for security people. We write it for everyone else.

Why this publication exists

Every week someone forwards a scary email to a relative and asks, “Is this real?” Usually it’s a scam. Sometimes it’s a real breach notice that looks like one. The person asking doesn’t need a lecture on attack chains. They need to know what happened, whether it affects them, and the next safe step. That’s the gap we cover.

Our starting belief is simple. You don’t need to understand every cyberattack. You need to recognize the risks that matter and know what to do next.

Who we write for

Families, parents, older adults and students. Freelancers and remote workers. Small professional offices, like law firms, dental practices, accountants and nonprofits, that handle sensitive information without an IT department. We’re based in South Carolina’s Grand Strand and write with Myrtle Beach and Conway in mind, but the advice applies wherever English-speaking readers get phished, from Ontario to Perth.

What we cover

Six sections: internet security, phishing, online scams, password security, multi-factor authentication, account protection. Inside them you’ll find email scams, identity theft, data breaches, QR-code fraud, business email compromise, mobile and browser security, and incident response basics for small organizations.

How briefings are written and checked

• Every claim about an incident links to a primary or established source. If a breach is unconfirmed, we say so.
• We don’t name anyone as an attacker without public evidence, and we never publish leaked personal data.
• Advice is defensive only. We don’t publish exploit steps, credential-theft methods or ways around security controls.
• We don’t inflate risk to get clicks. A risk level on a briefing reflects the evidence, not the headline.
• Corrections are made on the page with a dated note.

We are an independent publication. We are not a government department, agency or regulator, and nothing here should be read as official guidance. Headlines in our feed boxes belong to the outlets that published them. See our disclaimer for the details.

Who writes here

Got a tip, a scam sample or a correction? Reach the desk.