<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ZIA Networks</title>
    <description>The latest articles on DEV Community by ZIA Networks (@zianetworksinsight).</description>
    <link>https://dev.to/zianetworksinsight</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4011910%2F6fad64e0-ba58-4d28-aae4-8df4a180a4eb.jpeg</url>
      <title>DEV Community: ZIA Networks</title>
      <link>https://dev.to/zianetworksinsight</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zianetworksinsight"/>
    <language>en</language>
    <item>
      <title>The Cybersecurity Challenges Developers and Teams Will Face in 2027</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Thu, 12 Nov 2026 06:03:59 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/the-cybersecurity-challenges-developers-and-teams-will-face-in-2027-4afo</link>
      <guid>https://dev.to/zianetworksinsight/the-cybersecurity-challenges-developers-and-teams-will-face-in-2027-4afo</guid>
      <description>&lt;p&gt;Every year there's a wave of "the future of security" posts full of scary buzzwords. I'll skip that. My bet for 2027 is simpler: &lt;strong&gt;the biggest problems won't be exotic new attacks. They'll be old attacks, made faster, cheaper, and more convincing by AI.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Nobody can predict this perfectly, so treat this as an educated guess based on where things are heading. Here's what I'd watch, with practical fixes for each.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. AI-powered social engineering
&lt;/h2&gt;

&lt;p&gt;Phishing used to be easy to spot: broken grammar, odd sender, "Dear Customer." That tell is disappearing. Attackers can write flawless messages, clone a voice from a short clip, and run a convincing fake video call.&lt;/p&gt;

&lt;p&gt;As developers, we're targets too. Think of a "recruiter" sending a coding test with a malicious dependency or a fake "CTO" asking for urgent access.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What helps:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Verify requests for access, money, or credentials on a second channel.&lt;/li&gt;
&lt;li&gt;Run unknown code in a sandbox or container, not on your main machine.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Supply chain attacks hit your dependencies.
&lt;/h2&gt;

&lt;p&gt;You can write perfectly secure code and still get compromised through a package you installed or a CI action you copied from a README.&lt;/p&gt;

&lt;p&gt;A few habits go a long way:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Install exactly what's in the lockfile&lt;/span&gt;
npm ci

&lt;span class="c"&gt;# Check for known vulnerabilities&lt;/span&gt;
npm audit
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And in GitHub Actions, pin third-party actions to a full commit SHA instead of a movable tag:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="c1"&gt;# Risky: tag can be moved
&lt;/span&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;some-org/some-action@v2&lt;/span&gt;

&lt;span class="c1"&gt;# Safer: pinned to a specific commit
&lt;/span&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;some-org/some-action@&amp;lt;full-commit-sha&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Also consider generating an SBOM (software bill of materials) so you actually know what's in your builds.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Secrets leaking from repos and pipelines
&lt;/h2&gt;

&lt;p&gt;Hardcoded API keys in repos are still one of the most common ways in. Bots scan public commits within minutes.&lt;/p&gt;

&lt;p&gt;Catch them before they leave your machine:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Example: scan a repo with gitleaks&lt;/span&gt;
gitleaks detect --source .
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can also add it as a pre-commit hook and turn on your platform's built-in secret scanning and push protection.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rule of thumb:&lt;/strong&gt; if a secret was ever committed, treat it as compromised and rotate it. Deleting the commit isn't enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Identity is the new perimeter.
&lt;/h2&gt;

&lt;p&gt;Most breaches start with a stolen login, not a clever exploit. Passwords, session tokens, and MFA fatigue (spamming approval prompts until someone taps "yes") are all being abused.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What helps:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use phishing-resistant MFA (passkeys or hardware keys) for email, source control, cloud consoles, and admin accounts.&lt;/li&gt;
&lt;li&gt;Prefer short-lived credentials over long-lived keys.&lt;/li&gt;
&lt;li&gt;Apply least privilege. Your CI job probably doesn't need admin rights.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Shadow AI and unreviewed AI-generated code
&lt;/h2&gt;

&lt;p&gt;Two related problems here:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Data leaks.&lt;/strong&gt; People paste proprietary code, logs, or customer data into AI tools without thinking about where it goes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Blind trust.&lt;/strong&gt; AI-generated code can include insecure patterns, outdated libraries, or even packages that don't exist, which attackers can then register and fill with malware.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;What helps:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Set a clear, realistic policy on which AI tools are approved.&lt;/li&gt;
&lt;li&gt;Review AI-written code like any other pull request. Check that every dependency actually exists and is the one you intended.&lt;/li&gt;
&lt;li&gt;Never paste secrets or customer data into a prompt.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Ransomware that's about leaking, not locking
&lt;/h2&gt;

&lt;p&gt;Many attackers realised encryption is optional. Stealing your data and threatening to publish it works just as well, and backups don't fix that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What helps:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Store less sensitive data in the first place.&lt;/li&gt;
&lt;li&gt;Encrypt what you must keep.&lt;/li&gt;
&lt;li&gt;Keep offline, tested backups (and actually test the restore).&lt;/li&gt;
&lt;li&gt;Have an incident plan that includes legal and communications, not just engineering.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  7. Too many tools, too few people
&lt;/h2&gt;

&lt;p&gt;Most teams don't have a dedicated security group. They have a few busy people and a pile of dashboards nobody tunes. A lot of real risk comes from simple things left unpatched or misconfigured.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What helps:&lt;/strong&gt; automate patching and dependency updates, delete tools you don't use, and fix noisy alerts so the real ones get noticed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Phishing-resistant MFA on email, repos, cloud, and admin accounts&lt;/li&gt;
&lt;li&gt;[ ] Secret scanning and push protection enabled&lt;/li&gt;
&lt;li&gt;[ ] Dependencies locked, audited, and CI actions pinned&lt;/li&gt;
&lt;li&gt;[ ] Short-lived credentials and least privilege in pipelines&lt;/li&gt;
&lt;li&gt;[ ] Approved AI tool policy, plus review of AI-generated code&lt;/li&gt;
&lt;li&gt;[ ] Offline backups with a tested restore&lt;/li&gt;
&lt;li&gt;[ ] Written incident response plan&lt;/li&gt;
&lt;li&gt;[ ] Verification rule for money, access, and credential requests&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Final thoughts
&lt;/h2&gt;

&lt;p&gt;None of this is flashy. The boring basics stop most attacks, and the teams that get hurt in 2027 will mostly be the ones who knew what to do and never got around to it.&lt;/p&gt;

&lt;p&gt;I'd love to hear what you're seeing in practice. What's the security habit that saved your team, or the mistake you learned from the hard way? Let me know in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devops</category>
      <category>security</category>
    </item>
    <item>
      <title>SPF, DKIM, and DMARC Explained: Why Your Emails Land in Spam (or Get Spoofed)</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Wed, 11 Nov 2026 08:02:49 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/spf-dkim-and-dmarc-explained-why-your-emails-land-in-spam-or-get-spoofed-25l9</link>
      <guid>https://dev.to/zianetworksinsight/spf-dkim-and-dmarc-explained-why-your-emails-land-in-spam-or-get-spoofed-25l9</guid>
      <description>&lt;p&gt;You push a password reset flow to production, and users say they never got the email. Or a customer forwards you a message that looks like it came from your company, but you never sent it.&lt;/p&gt;

&lt;p&gt;Both problems usually come from &lt;strong&gt;missing or misconfigured email authentication&lt;/strong&gt;. At &lt;strong&gt;Zia Networks&lt;/strong&gt;, this is one of the most common issues we see in business email setups and one of the easiest to fix once you understand it.&lt;/p&gt;

&lt;p&gt;In this post, we'll cover what SPF, DKIM, and DMARC are, how they work together, and how to set them up step by step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Email Authentication Matters
&lt;/h2&gt;

&lt;p&gt;Email was designed in the 1980s, and SMTP has &lt;strong&gt;no built-in way to verify who is really sending a message&lt;/strong&gt;. Anyone can set the &lt;code&gt;address&lt;/code&gt; to &lt;code&gt;ceo@yourcompany.com&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;That leads to two problems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Spoofing and phishing:&lt;/strong&gt; attackers impersonate your domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Spam filtering:&lt;/strong&gt; Gmail, Outlook, and Yahoo distrust unauthenticated mail, so even legitimate emails get junked.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;SPF, DKIM, and DMARC are three DNS-based standards that solve this together.&lt;/p&gt;

&lt;h2&gt;
  
  
  SPF: Who Can Send Email for Your Domain?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;SPF (Sender Policy Framework)&lt;/strong&gt; is a DNS TXT record listing the servers and services allowed to send email for your domain.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;v=spf1 include:_spf.google.com include:sendgrid.net -all
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Part&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;v=spf1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Identifies the record as SPF&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;include:&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Authorises a third-party sender&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;-all&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Reject everything else (&lt;code&gt;~all&lt;/code&gt; = soft fail)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Common SPF mistakes
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Multiple SPF records.&lt;/strong&gt; Only one is allowed per domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;More than 10 DNS lookups.&lt;/strong&gt; Too many &lt;code&gt;include:&lt;/code&gt; entries break SPF.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forgotten senders.&lt;/strong&gt; CRM, newsletter tool, helpdesk, and so on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Using &lt;code&gt;+all&lt;/code&gt;.&lt;/strong&gt; This authorises the entire internet.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Check your current record from the terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig +short TXT yourcompany.com &lt;span class="o"&gt;|&lt;/span&gt; grep spf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Limitation:&lt;/strong&gt; SPF checks the hidden envelope sender, not the visible ``address, and it often breaks on forwarded mail.&lt;/p&gt;

&lt;h2&gt;
  
  
  DKIM: Was the Email Tampered With?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;DKIM (DomainKeys Identified Mail)&lt;/strong&gt; adds a digital signature to every outgoing message, like a wax seal on a letter.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Your mail server signs the message with a &lt;strong&gt;private key&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;You publish the &lt;strong&gt;public key&lt;/strong&gt; in DNS.&lt;/li&gt;
&lt;li&gt;The receiver verifies the signature using that public key.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;`plaintext&lt;br&gt;
Name:  selector1._domainkey.yourcompany.com&lt;br&gt;
Type:  TXT&lt;br&gt;
Value: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQ...&lt;br&gt;
`&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;selector1&lt;/code&gt; part is the &lt;strong&gt;selector&lt;/strong&gt;, which lets you run multiple keys, for example, one per email service.&lt;/p&gt;

&lt;p&gt;Look up a DKIM record:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;`bash&lt;br&gt;
dig +short TXT selector1._domainkey.yourcompany.com&lt;br&gt;
`&lt;/code&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Common DKIM mistakes
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Enabling DKIM in the provider but &lt;strong&gt;never publishing the DNS record&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Using weak 512-bit keys (use &lt;strong&gt;2048-bit&lt;/strong&gt;)&lt;/li&gt;
&lt;li&gt;Never rotating keys&lt;/li&gt;
&lt;li&gt;Skipping DKIM for third-party senders&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
  
  
  DMARC: What Happens When a Check Fails?
&lt;/h2&gt;

&lt;p&gt;SPF and DKIM verify mail, but neither says what to do on failure. &lt;strong&gt;DMARC (Domain-based Message Authentication, Reporting &amp;amp; Conformance)&lt;/strong&gt; adds:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Alignment:&lt;/strong&gt; the visible ``domain must match the domain verified by SPF or DKIM.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Policy:&lt;/strong&gt; monitor, quarantine, or reject failing mail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reporting:&lt;/strong&gt; reports showing who sends emails to your domain.
&lt;/li&gt;
&lt;/ol&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Name:  _dmarc.yourcompany.com
Type:  TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourcompany.com; pct=100
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Policy&lt;/th&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;th&gt;When to use&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;p=none&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Monitor only&lt;/td&gt;
&lt;td&gt;Starting out&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;p=quarantine&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Failing mail goes to spam&lt;/td&gt;
&lt;td&gt;After fixing legitimate senders&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;p=reject&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Failing mail is blocked&lt;/td&gt;
&lt;td&gt;Full spoofing protection&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;DMARC passes if &lt;strong&gt;either&lt;/strong&gt; SPF &lt;strong&gt;or&lt;/strong&gt; DKIM passes &lt;strong&gt;and&lt;/strong&gt; aligns with the &lt;code&gt;From&lt;/code&gt; domain.&lt;br&gt;
&lt;/p&gt;


&lt;/blockquote&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dig +short TXT _dmarc.yourcompany.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  How They Work Together
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SPF&lt;/strong&gt; checks &lt;em&gt;where&lt;/em&gt; the email came from.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DKIM&lt;/strong&gt; checks the email &lt;em&gt;wasn't altered&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DMARC&lt;/strong&gt; checks the results &lt;em&gt;match the visible 'From' address&lt;/em&gt; and enforces a policy.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No single one is enough. Together they protect your brand and improve deliverability.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Your Emails Land in Spam
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;No SPF, DKIM, or DMARC at all (Google and Yahoo now require authentication for bulk senders)&lt;/li&gt;
&lt;li&gt;SPF or DKIM failures from misconfiguration or a missing sender&lt;/li&gt;
&lt;li&gt;Alignment failures, where a third-party tool sends using its own domain&lt;/li&gt;
&lt;li&gt;Poor domain or IP reputation&lt;/li&gt;
&lt;li&gt;Content and list issues, such as spammy wording or purchased lists&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why Your Domain Gets Spoofed
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No DMARC record, or one stuck on &lt;code&gt;p=none&lt;/code&gt; forever&lt;/li&gt;
&lt;li&gt;A weak SPF record with no DMARC backup&lt;/li&gt;
&lt;li&gt;Unprotected subdomains and parked domains&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step-by-Step Setup
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Inventory every sender:&lt;/strong&gt; mailbox provider, marketing tool, CRM, billing, helpdesk, and website forms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Publish one clean SPF record&lt;/strong&gt; under the 10-lookup limit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enable DKIM for every sender&lt;/strong&gt; and test it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start DMARC at &lt;code&gt;p=none&lt;/code&gt;&lt;/strong&gt; with a reporting address, and collect data for 2 to 4 weeks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Analyse the reports&lt;/strong&gt; and fix legitimate senders that fail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move gradually:&lt;/strong&gt; &lt;code&gt;none&lt;/code&gt; → &lt;code&gt;quarantine&lt;/code&gt; (start with &lt;code&gt;pct=10&lt;/code&gt;) → &lt;code&gt;reject&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Monitor continuously.&lt;/strong&gt; New vendors mean new sending sources.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Testing Your Setup
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://mxtoolbox.com/" rel="noopener noreferrer"&gt;MXToolbox&lt;/a&gt; for SPF, DKIM, and DMARC lookups&lt;/li&gt;
&lt;li&gt;Send a test email to Gmail and click &lt;strong&gt;'Show original'&lt;/strong&gt; to see pass or fail results.&lt;/li&gt;
&lt;li&gt;DMARC report analysers to turn raw XML into dashboards&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] One SPF record, under 10 lookups&lt;/li&gt;
&lt;li&gt;[ ] DKIM enabled for every sending service&lt;/li&gt;
&lt;li&gt;[ ] DMARC published with a reporting address&lt;/li&gt;
&lt;li&gt;[ ] Policy moving toward &lt;code&gt;quarantine&lt;/code&gt; or &lt;code&gt;reject&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Subdomains and parked domains covered&lt;/li&gt;
&lt;li&gt;[ ] DMARC reports are reviewed regularly.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;SPF, DKIM, and DMARC answer three simple questions: &lt;strong&gt;Who can send for you? Is the message authentic? And what happens if it isn't?&lt;/strong&gt; Get them right and you'll see fewer emails in spam, far less impersonation risk, and a stronger domain reputation.&lt;/p&gt;

&lt;p&gt;If you'd rather not untangle DNS records and DMARC reports alone, the team at &lt;strong&gt;&lt;a href="https://www.zianetworks.net/blog/spf-dkim-and-dmarc-explained-why-your-emails-land-in-spam/" rel="noopener noreferrer"&gt;Zia Networks&lt;/a&gt;&lt;/strong&gt; can audit your email authentication, fix misconfigurations, and guide you to full DMARC enforcement.&lt;/p&gt;

&lt;p&gt;Have you run into tricky SPF lookup limits or DMARC alignment issues? Share your experience in the comments. 👇&lt;/p&gt;

</description>
      <category>security</category>
      <category>devops</category>
    </item>
    <item>
      <title>Nonprofit IT on a Budget: A Developer's Guide to Funder and Compliance Requirements</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Tue, 10 Nov 2026 06:56:10 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/nonprofit-it-on-a-budget-a-developers-guide-to-funder-and-compliance-requirements-4an1</link>
      <guid>https://dev.to/zianetworksinsight/nonprofit-it-on-a-budget-a-developers-guide-to-funder-and-compliance-requirements-4an1</guid>
      <description>&lt;p&gt;If you work in tech, someone has probably asked you to “just help with the IT” for a nonprofit. Maybe you volunteer for one, maybe a friend runs a small charity, or maybe you were hired as an office manager and inherited the router. Then a grant arrives with a security clause, or an insurer asks whether the team uses multi-factor authentication, and the honest answer is “we’re working on it.”&lt;/p&gt;

&lt;p&gt;This post is a practical plan for that situation. The goal isn’t an enterprise security programme. It’s to cover the fundamentals, spend as little as possible, and keep evidence that you did the work. At ZIA Networks, we think of this as the heart of nonprofit IT on a budget: do the basics, then prove it.&lt;/p&gt;

&lt;p&gt;Step 1: Scope your obligations first.&lt;/p&gt;

&lt;p&gt;“Compliance” isn’t one thing. What applies depends on the data you hold and where you operate. Answer four questions:&lt;/p&gt;

&lt;p&gt;What data do we hold? Donor payments, health information, and children’s records carry very different risks.&lt;br&gt;
Where are our people and funders? Depending on location, GDPR, US state privacy laws, India’s data protection rules, or FCRA (for foreign contributions) may apply.&lt;br&gt;
What do our grant agreements require? Funding contracts often include technology and data clauses nobody reads until reporting time.&lt;br&gt;
Do we accept card payments? Your payment processor usually carries most of the burden, but you still follow its rules.&lt;/p&gt;

&lt;p&gt;Write the answers on one page. Treat it like a requirements doc. Every later decision should trace back to it.&lt;/p&gt;

&lt;p&gt;Step 2: Build an asset and access inventory.&lt;/p&gt;

&lt;p&gt;You can’t secure what you haven’t listed. A spreadsheet is fine:&lt;/p&gt;

&lt;p&gt;System  Data: It holds  who has access to the   owner.&lt;br&gt;
Donor CRM   names, giving history   Fundraising team    Development lead&lt;br&gt;
Email platform: Everything  All staff   admin&lt;br&gt;
Shared drive    mixed files Unknown Unknown&lt;/p&gt;

&lt;p&gt;The “Unknown” rows are where your risk lives. Expect to find a former volunteer with admin rights, a personal cloud account used “temporarily,” and a shared drive nobody has audited in years. Auditors and funders ask for exactly this.&lt;/p&gt;

&lt;p&gt;Step 3: Ship the high-impact, low-cost controls.&lt;/p&gt;

&lt;p&gt;MFA. Enable it on email, your CRM, banking, and cloud storage first. Prefer authenticator apps or hardware keys over SMS when possible. It’s usually a free setting and the single most valuable step.&lt;/p&gt;

&lt;p&gt;Password manager. Replace shared spreadsheets and sticky notes. It makes offboarding far easier, because you revoke access instead of rotating every shared password and hoping people comply.&lt;/p&gt;

&lt;p&gt;Patching. Turn on automatic updates for operating systems, browsers, and apps. Track exceptions, like old machines or unsupported software, in your inventory.&lt;/p&gt;

&lt;p&gt;Backups. Follow 3-2-1: three copies, two storage types, one offsite. Then test a restore. An untested backup is an assumption, not a control.&lt;/p&gt;

&lt;p&gt;Least privilege. Give each person only what their role needs. An event volunteer doesn’t need donor-giving history. Review permissions twice a year and remove accounts the day someone leaves.&lt;/p&gt;

&lt;p&gt;Device encryption. Modern laptops and phones include built-in full-disc encryption. Turning it on takes minutes and can turn a lost device from a reportable breach into an inconvenience.&lt;/p&gt;

&lt;p&gt;Step 4: Claim nonprofit discounts.&lt;/p&gt;

&lt;p&gt;Check TechSoup and similar regional programmes, Google for Nonprofits, Microsoft’s nonprofit offers, and credits from cloud and security vendors. Volunteer IT networks can sometimes do a one-time review for free. Offers and eligibility change, so confirm current terms with each provider.&lt;/p&gt;

&lt;p&gt;Step 5: Write policies people will actually follow.&lt;/p&gt;

&lt;p&gt;A one-page policy everyone follows beats a 40-page one nobody reads. Start with four:&lt;/p&gt;

&lt;p&gt;Acceptable use: what staff and volunteers may do with devices and accounts&lt;br&gt;
Data handling: what you collect, why, how long you keep it, who sees it&lt;br&gt;
Incident response: who to call and what to do first&lt;br&gt;
Onboarding and offboarding: how access is granted and, more importantly, revoked&lt;/p&gt;

&lt;p&gt;Start from free templates, then edit them to describe what your team really does.&lt;/p&gt;

&lt;p&gt;Step 6: Train the humans.&lt;/p&gt;

&lt;p&gt;Most incidents at small organisations aren’t clever exploits. They’re convincing phishing emails, files sent to the wrong person, and reused passwords. A 30-minute session once or twice a year, using real phishing examples, helps. Culture matters more than content: make it safe to say “I think I clicked something bad.” Early reports limit damage, and training records are good evidence for funders.&lt;/p&gt;

&lt;p&gt;Step 7: Keep evidence as you go&lt;/p&gt;

&lt;p&gt;Compliance is mostly about showing consistent, reasonable effort. Keep one evidence folder with:&lt;/p&gt;

&lt;p&gt;Your requirements summary and inventory&lt;br&gt;
Current policies with review dates&lt;br&gt;
Training dates, topics, and attendees&lt;br&gt;
Access review notes&lt;br&gt;
Backup test results&lt;br&gt;
Step 8: Know when to bring in professionals&lt;/p&gt;

&lt;p&gt;Consider paid help if you hold sensitive data (health, immigration, financial, or children’s records), a funder requires a formal assessment, you’re migrating systems, or you’ve outgrown volunteer-only IT. A part-time consultant or managed IT provider, such as ZIA Networks, can take on monitoring, security, and compliance support. Whoever you pick, ask about nonprofit pricing and plain-language reporting you can hand to funders.&lt;/p&gt;

&lt;p&gt;Step 9: Make it a routine&lt;br&gt;
Quarterly: review access and run a backup restore test (about 30 minutes).&lt;br&gt;
Twice a year: permissions review&lt;br&gt;
Annually: policy review and training refresher&lt;br&gt;
Every departure: remove accounts the same day.&lt;br&gt;
TL;DR&lt;br&gt;
Scope your obligations before buying anything.&lt;br&gt;
Inventory systems, data, and access.&lt;br&gt;
Start with MFA, a password manager, updates, tested backups, least privilege, and encryption.&lt;br&gt;
Keep policies short and honest, and train without blame.&lt;br&gt;
Collect evidence continuously, not only before audits.&lt;/p&gt;

&lt;p&gt;Pick one step this week. Enabling MFA or building the inventory are both great starting points.&lt;/p&gt;

&lt;p&gt;Question for you: What’s the hardest IT or compliance problem you’ve run into at a small organisation? Tell me in the comments, and I’ll cover the most common ones in a follow-up.&lt;/p&gt;

&lt;p&gt;Disclosure: I work with ZIA Networks, which supports nonprofits with IT and compliance planning. This post is general information, not legal or compliance advice. Confirm your specific obligations with your funders, legal counsel, or a qualified professional.&lt;/p&gt;

</description>
      <category>security</category>
      <category>beginners</category>
      <category>openai</category>
      <category>devops</category>
    </item>
    <item>
      <title>Is Your Old Computer Still Safe? What Unsupported Windows Versions Mean for Your Business</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Wed, 04 Nov 2026 06:59:59 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/is-your-old-computer-still-safe-what-unsupported-windows-versions-mean-for-your-business-4noh</link>
      <guid>https://dev.to/zianetworksinsight/is-your-old-computer-still-safe-what-unsupported-windows-versions-mean-for-your-business-4noh</guid>
      <description>&lt;p&gt;The Windows box in the corner that runs the legacy app. The PC wired to the lab instrument. The machine that hosts a script nobody wants to migrate because "it just works".&lt;/p&gt;

&lt;p&gt;It boots every morning. Nobody complains. And that's exactly why it's dangerous.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"It still works" and "it's still safe" are two very different statements.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What "end of support" actually means
&lt;/h2&gt;

&lt;p&gt;When Microsoft ends support for a Windows version, nothing visibly happens. No shutdown, no banner, no countdown. The machine just stops receiving security patches.&lt;/p&gt;

&lt;p&gt;Here's where the common versions stand:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Version&lt;/th&gt;
&lt;th&gt;Support ended&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Windows 7&lt;/td&gt;
&lt;td&gt;January 2020&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Windows 8.1&lt;/td&gt;
&lt;td&gt;January 2023&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Windows 10&lt;/td&gt;
&lt;td&gt;October 14, 2025&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Windows 10 has a paid Extended Security Updates (ESU) programme as a bridge. It's per-device, time-limited, and gets pricier over time, so think of it as a way to buy time rather than a plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why unpatched Windows is a real problem
&lt;/h2&gt;

&lt;p&gt;If you've read a CVE advisory, you know how this goes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A flaw is found and patched on supported versions.&lt;/li&gt;
&lt;li&gt;The patch and advisory make the flaw public.&lt;/li&gt;
&lt;li&gt;Attackers build exploits and scan for machines that never got the fix.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Supported systems are covered after step 1. Unsupported ones stay exposed to everything from step 2 onward, forever.&lt;/p&gt;

&lt;p&gt;And the machine doesn't have to be valuable to be dangerous. It just has to be &lt;strong&gt;reachable&lt;/strong&gt;. A single unpatched endpoint is a classic foothold for ransomware to move toward file servers, credentials, and backups.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Antivirus and EDR can detect and respond. They can't patch a vulnerable OS component.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Find what you actually have
&lt;/h2&gt;

&lt;p&gt;You can't secure what you don't know about. For domain-joined machines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-ADComputer&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Filter&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s1"&gt;'OperatingSystem -like "*Windows*"'&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="se"&gt;`
&lt;/span&gt;&lt;span class="w"&gt;  &lt;/span&gt;&lt;span class="nt"&gt;-Properties&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;OperatingSystem&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;OperatingSystemVersion&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;LastLogonDate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;OperatingSystem&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;OperatingSystemVersion&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;LastLogonDate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Sort-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;OperatingSystem&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Export-Csv&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;\windows-inventory.csv&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-NoTypeInformation&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For a single machine:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-CimInstance&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Win32_OperatingSystem&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Caption&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Version&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;BuildNumber&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then go looking for the machines AD can't see: standalone PCs, kiosks, point-of-sale terminals, and anything attached to specialized equipment. The ones with a &lt;code&gt;LastLogonDate&lt;/code&gt; from months ago are usually the forgotten ones, and the forgotten ones are the risky ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can it run Windows 11?
&lt;/h2&gt;

&lt;p&gt;Windows 11 needs TPM 2.0, Secure Boot, and a supported CPU. A quick local check:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-Tpm&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;TpmPresent&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;TpmReady&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;Confirm-SecureBootUEFI&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On legacy BIOS systems, it throws an error, which tells you something on its own. For the full answer, including CPU support, use Microsoft's PC Health Check app or your endpoint tool's readiness report.&lt;/p&gt;

&lt;p&gt;Then sort every machine into one of three buckets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Upgrade:&lt;/strong&gt; meets the requirements, so upgrade in place&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replace:&lt;/strong&gt; hardware can't run Windows 11, so budget for a new device.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Special case:&lt;/strong&gt; tied to a legacy app or device, so contain it and plan&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Contain what you can't replace yet
&lt;/h2&gt;

&lt;p&gt;Some machines genuinely can't move today. Proprietary drivers, vendor lock-in, a tool that only runs on an old OS. If that's you, shrink the blast radius:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Put it on an isolated VLAN with strict ACLs.&lt;/li&gt;
&lt;li&gt;Block outbound internet unless there's a documented need&lt;/li&gt;
&lt;li&gt;No email, no browsing on that machine&lt;/li&gt;
&lt;li&gt;Remove everyday admin rights and restrict logins&lt;/li&gt;
&lt;li&gt;Keep backups offline or immutable.&lt;/li&gt;
&lt;li&gt;Ship its logs somewhere central and alert on weird traffic&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;⚠️ This &lt;strong&gt;reduces&lt;/strong&gt; risk. It doesn't &lt;strong&gt;remove&lt;/strong&gt; it. Treat it as a seatbelt on a car with bad brakes: better than nothing, not a long-term plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Don't let "temporary" become "forever".
&lt;/h2&gt;

&lt;p&gt;My favourite low-tech fix is an exception register. A simple table in your repo or wiki:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Hostname&lt;/th&gt;
&lt;th&gt;OS&lt;/th&gt;
&lt;th&gt;Why it can't move&lt;/th&gt;
&lt;th&gt;Owner&lt;/th&gt;
&lt;th&gt;Controls&lt;/th&gt;
&lt;th&gt;Review date&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;LAB-PC-01&lt;/td&gt;
&lt;td&gt;Windows 7&lt;/td&gt;
&lt;td&gt;Vendor driver&lt;/td&gt;
&lt;td&gt;J. Doe&lt;/td&gt;
&lt;td&gt;VLAN 40, no internet&lt;/td&gt;
&lt;td&gt;2027-01-31&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Every exception gets an &lt;strong&gt;owner&lt;/strong&gt; and a &lt;strong&gt;review date&lt;/strong&gt;. Without those, "we'll fix it next quarter" quietly turns into five years.&lt;/p&gt;

&lt;h2&gt;
  
  
  The non-technical argument (for when you need budget)
&lt;/h2&gt;

&lt;p&gt;If you're making the case to management, these usually land:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Compliance:&lt;/strong&gt; PCI DSS, HIPAA, and GDPR all expect reasonable patching.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Insurance:&lt;/strong&gt; cyber insurers increasingly ask about unsupported systems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Support drift:&lt;/strong&gt; browsers and business apps eventually drop old Windows versions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Productivity:&lt;/strong&gt; old hardware crashes and lags, and the lost minutes add up.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A ransomware incident costs far more than a replacement cycle spread over a few quarters.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Inventory everything, including the forgotten machines.&lt;/li&gt;
&lt;li&gt;Sort into Upgrade / Replace / Special Case&lt;/li&gt;
&lt;li&gt;Isolate what can't move, and write down who owns it.&lt;/li&gt;
&lt;li&gt;Replace on a schedule, starting with the most exposed machines.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Unsupported machines don't fail loudly. They sit there working while the risk grows. The fix is boring, and that's a good thing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Have you dealt with a stubborn legacy Windows dependency? How did you handle it? Let me know in the comments.&lt;/strong&gt; 👇&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>beginners</category>
      <category>sysadmin</category>
    </item>
    <item>
      <title>A 30-Minute Ransomware Self-Audit for Small Business Networks</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Tue, 03 Nov 2026 14:05:26 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/a-30-minute-ransomware-self-audit-for-small-business-networks-4klm</link>
      <guid>https://dev.to/zianetworksinsight/a-30-minute-ransomware-self-audit-for-small-business-networks-4klm</guid>
      <description>&lt;p&gt;Small businesses, like the shops and offices around Santa Fe, New Mexico,&lt;br&gt;
often have no dedicated security team. If you're the dev or admin, everyone asks for help, here are five checks that take about 30 minutes in total and&lt;br&gt;
Cover the weak points automated ransomware attacks go after.&lt;/p&gt;

&lt;p&gt;Ransomware campaigns mostly don't pick victims by location. Automated&lt;br&gt;
scanners look for exposed services, leaked passwords, and old software, and&lt;br&gt;
Whoever shows up gets hit. So the goal is simple: &lt;strong&gt;don't show up&lt;/strong&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Only run these checks on systems and networks you own or are authorized&lt;br&gt;
to test.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;
  
  
  1. Is anything dangerous exposed to the internet?
&lt;/h2&gt;

&lt;p&gt;From a machine outside your network, scan your own public IP for commonly&lt;br&gt;
abused ports:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;nmap &lt;span class="nt"&gt;-p&lt;/span&gt; 22,445,3389 &amp;lt;your-public-ip&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Remote Desktop (3389) and SMB (445) should not be reachable from the open&lt;br&gt;
internet. If they are, put remote access behind a VPN with MFA and close the&lt;br&gt;
ports on the router or firewall.&lt;/p&gt;
&lt;h2&gt;
  
  
  2. Is Remote Desktop enabled where it shouldn't be?
&lt;/h2&gt;

&lt;p&gt;On a Windows machine (&lt;code&gt;0&lt;/code&gt; means remote connections are allowed):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-ItemProperty&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s1"&gt;'HKLM:\System\CurrentControlSet\Control\Terminal Server'&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="se"&gt;`
&lt;/span&gt;&lt;span class="w"&gt;  &lt;/span&gt;&lt;span class="nt"&gt;-Name&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;fDenyTSConnections&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Has anyone set up a sneaky mail forwarding rule?
&lt;/h2&gt;

&lt;p&gt;Attackers who get into a mailbox often add a forwarding rule to watch&lt;br&gt;
conversations and redirect payments. In Exchange Online PowerShell:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-InboxRule&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="nx"&gt;yourdomain.com&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Where-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;RedirectTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardAsAttachmentTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you find a rule nobody created, treat it as a possible compromise: reset&lt;br&gt;
the password, revoke sessions, and investigate.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. How old are your updates?
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Windows: most recent patches&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;Get-HotFix&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Sort-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;InstalledOn&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Descending&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-First&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;5&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Debian/Ubuntu: pending upgrades&lt;/span&gt;
apt list &lt;span class="nt"&gt;--upgradable&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Don't forget routers, firewalls, and NAS devices. They are common entry.&lt;br&gt;
points and often run firmware that's years out of date.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Can you actually restore from backup?
&lt;/h2&gt;

&lt;p&gt;This is the check people skip. Pick one file or system and restore it from&lt;br&gt;
your backup into a test location. Then confirm that at least one copy is&lt;br&gt;
offline or immutable, so ransomware can't encrypt or delete it. A backup you&lt;br&gt;
have never restored from is a guess, not a plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick wins to do next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Turn on MFA for email, cloud storage, banking, and remote access.&lt;/li&gt;
&lt;li&gt;Use a password manager to end password reuse.&lt;/li&gt;
&lt;li&gt;Limit admin rights to the people who need them&lt;/li&gt;
&lt;li&gt;Write a one-page incident plan: who to call and how to isolate machines.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  If you are hit
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Disconnect affected machines from the network.&lt;/li&gt;
&lt;li&gt;Don't wipe anything yet. You may need it for forensics.&lt;/li&gt;
&lt;li&gt;Contact your IT provider or an incident response firm.&lt;/li&gt;
&lt;li&gt;Report it to the FBI's IC3 at &lt;a href="https://www.ic3.gov" rel="noopener noreferrer"&gt;https://www.ic3.gov&lt;/a&gt; and notify your insurer.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Wrap-up
&lt;/h2&gt;

&lt;p&gt;Five checks won't make you bulletproof, but they close the doors that most&lt;br&gt;
automated attacks try first. What's the first thing you'd fix on your own?&lt;br&gt;
network? Tell me in the comments.&lt;/p&gt;

&lt;p&gt;*Disclosure: I used AI assistance to draft this article. I reviewed it.&lt;br&gt;
checked the facts, and tested the commands myself. *&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The Hidden Cost of Cheap IT: What a Day of Downtime Costs a Santa Fe Business | ZIA Networks</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Mon, 02 Nov 2026 06:56:12 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/the-hidden-cost-of-cheap-it-what-a-day-of-downtime-costs-a-santa-fe-business-zia-networks-102m</link>
      <guid>https://dev.to/zianetworksinsight/the-hidden-cost-of-cheap-it-what-a-day-of-downtime-costs-a-santa-fe-business-zia-networks-102m</guid>
      <description>&lt;p&gt;It's 8:15 on a Tuesday morning. The coffee is hot, the day is mapped out, and&lt;br&gt;
Then your front desk person walks over with a puzzled look. "The computers are&lt;br&gt;
acting weird."&lt;br&gt;
Within minutes, email stops. The phones, which run over the internet, go quiet.&lt;br&gt;
Somebody asks, "Did we forget to pay the internet bill?" and for a moment,&lt;br&gt;
Everyone hopes that's all it is.&lt;/p&gt;

&lt;p&gt;Most of the time, it's not.&lt;/p&gt;

&lt;p&gt;At &lt;strong&gt;ZIA Networks&lt;/strong&gt;, we've watched this exact morning unfold at businesses all&lt;br&gt;
over Santa Fe. What catches owners off guard isn't the outage itself. It's the&lt;br&gt;
&lt;strong&gt;Santa Fe IT downtime costs&lt;/strong&gt; that pile up afterward, most of which never&lt;br&gt;
shows up on a single invoice.&lt;/p&gt;

&lt;p&gt;If you work in IT, DevOps, or support, this is the conversation you may need to&lt;br&gt;
have with a client or boss. So here's the math in plain terms.&lt;/p&gt;
&lt;h2&gt;
  
  
  IT isn't an expense. It's the floor you stand on.
&lt;/h2&gt;

&lt;p&gt;Owners often treat IT as a monthly cost to keep low. So when someone offers a&lt;br&gt;
plan at half the price, it feels like a win.&lt;/p&gt;

&lt;p&gt;But when IT fails, you don't lose "tech". You lose the whole day.&lt;/p&gt;
&lt;h2&gt;
  
  
  The math
&lt;/h2&gt;

&lt;p&gt;These numbers are made up for illustration, but they're realistic for a small&lt;br&gt;
business. Swap in your own.&lt;/p&gt;

&lt;p&gt;Picture a 10-person office earning about $1.8 million a year. Over roughly 250&lt;br&gt;
working days, that's about &lt;strong&gt;$7,200 on a normal day&lt;/strong&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What one day offline costs&lt;/th&gt;
&lt;th&gt;Estimate&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Idle payroll (10 people, 8 hours)&lt;/td&gt;
&lt;td&gt;$3,200&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lost or delayed revenue&lt;/td&gt;
&lt;td&gt;$3,600&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Emergency IT help&lt;/td&gt;
&lt;td&gt;$1,000 - $1,500&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Catch-up work and overtime&lt;/td&gt;
&lt;td&gt;About $800&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;About $9,000 - $9,500&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;
&lt;h2&gt;
  
  
  A tiny calculator you can run
&lt;/h2&gt;

&lt;p&gt;Here's a quick Python version so you can plug in a client's real numbers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;downtime_cost&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;staff&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;hourly&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;40&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;8&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                  &lt;span class="n"&gt;annual_revenue&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;1_800_000&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;work_days&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;250&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                  &lt;span class="n"&gt;share_lost&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mf"&gt;0.5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;emergency_it&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;1250&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;catch_up&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;800&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;idle_payroll&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;staff&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;hourly&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt;
    &lt;span class="n"&gt;lost_revenue&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;annual_revenue&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="n"&gt;work_days&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;share_lost&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;idle_payroll&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;lost_revenue&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;emergency_it&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;catch_up&lt;/span&gt;

&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Estimated cost of one day offline: $&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;downtime_cost&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="si"&gt;:&lt;/span&gt;&lt;span class="p"&gt;,.&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="c1"&gt;# Estimated cost of one day offline: $9,250
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And that only covers what you can count.&lt;/p&gt;

&lt;h2&gt;
  
  
  The costs that don't fit in a spreadsheet
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Customers who quietly leave.&lt;/strong&gt; They rarely complain. They just stop calling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team stress.&lt;/strong&gt; Good employees remember days like that.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data you can't get back.&lt;/strong&gt; A backup that has never been tested isn't a
backup. It's a hope.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compliance trouble&lt;/strong&gt; if you handle client, health, or financial records.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why a small market like Santa Fe has its own version of this problem
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Older adobe and historic buildings with wiring never planned for modern offices&lt;/li&gt;
&lt;li&gt;Monsoon season power flickers and lightning strikes&lt;/li&gt;
&lt;li&gt;Patchy internet outside the main corridors&lt;/li&gt;
&lt;li&gt;A smaller market, so there's often no backup if your only IT person is away&lt;/li&gt;
&lt;li&gt;Tourism businesses can't make up a lost peak-season Saturday later&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What "cheap IT" usually leaves out
&lt;/h2&gt;

&lt;p&gt;Low price isn't the enemy. But the cheap kind often quietly cuts what you can't.&lt;br&gt;
see:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Active monitoring, so problems get caught before staff notice&lt;/li&gt;
&lt;li&gt;[ ] Backups that are regularly test-restored&lt;/li&gt;
&lt;li&gt;[ ] Real response times, not "within 48 hours"&lt;/li&gt;
&lt;li&gt;[ ] Written documentation of the setup&lt;/li&gt;
&lt;li&gt;[ ] Regular updates and security patches&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this hurts on a good day. That's exactly why it feels fine until it&lt;br&gt;
doesn't.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five questions to ask this week
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;If everything went down at 9 a.m., who would I call, and how fast would they
Really respond?&lt;/li&gt;
&lt;li&gt;When did someone last test restore from our backup?&lt;/li&gt;
&lt;li&gt;Do I know what a full day of downtime costs us?&lt;/li&gt;
&lt;li&gt;Is our setup written down somewhere?&lt;/li&gt;
&lt;li&gt;Is anyone watching for problems before we notice?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you hesitated on more than two, it's worth a conversation before a bad&lt;br&gt;
Tuesday starts one for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real math
&lt;/h2&gt;

&lt;p&gt;Better IT support might cost a few hundred dollars more each month. One bad day&lt;br&gt;
can cost $10,000 or more. If that happens even once every few years, the&lt;br&gt;
The "expensive" option often pays for itself.&lt;/p&gt;

&lt;p&gt;The cheapest IT isn't the plan with the lowest price. It's the one you rarely&lt;br&gt;
think about, because it just works, and when it doesn't, someone is already on&lt;br&gt;
it.&lt;/p&gt;

&lt;p&gt;Grab a calculator (or the snippet above) and work out what &lt;em&gt;your&lt;/em&gt; Tuesday would&lt;br&gt;
cost. If the number gets your attention, the team at &lt;strong&gt;ZIA Networks&lt;/strong&gt; is happy.&lt;br&gt;
to walk through it with you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Contact ZIA Networks:&lt;/strong&gt; [&lt;a href="https://www.zianetworks.net/blog/the-hidden-cost-of-cheap-it-what-a-day-of-downtime-actually-costs" rel="noopener noreferrer"&gt;https://www.zianetworks.net/blog/the-hidden-cost-of-cheap-it-what-a-day-of-downtime-actually-costs&lt;/a&gt;]&lt;/p&gt;




&lt;p&gt;&lt;em&gt;What's the worst downtime story you've seen? Share it in the comments. I'd&lt;br&gt;
love to hear how it played out.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devops</category>
      <category>cybersecurity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Passkeys for Developers: How WebAuthn Works and How to Add It to Your App</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Thu, 29 Oct 2026 07:20:56 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/passkeys-for-developers-how-webauthn-works-and-how-to-add-it-to-your-app-14mi</link>
      <guid>https://dev.to/zianetworksinsight/passkeys-for-developers-how-webauthn-works-and-how-to-add-it-to-your-app-14mi</guid>
      <description>&lt;p&gt;Passwords are a liability. Users reuse them, phishing kits harvest them, and your database becomes a target the moment you store anything derived from them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Passkeys&lt;/strong&gt; replace the shared secret with public-key cryptography. In this post we'll cover how they work, then walk through registering and signing in with the browser's WebAuthn API.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The browser code below is the real WebAuthn API. The server side is described and not fully implemented on purpose: use a maintained library rather than writing signature and attestation verification yourself.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The Mental Model
&lt;/h2&gt;

&lt;p&gt;A passkey is a &lt;strong&gt;key pair&lt;/strong&gt; created per site (per &lt;em&gt;relying party&lt;/em&gt;):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;private key&lt;/strong&gt; stays on the user's device (or in their synced credential manager). It never leaves.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;public key&lt;/strong&gt; is stored on your server, along with a credential ID.&lt;/li&gt;
&lt;li&gt;To sign in, your server sends a random &lt;strong&gt;challenge&lt;/strong&gt;. The device signs it. Your server verifies the signature with the stored public key.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because the credential is bound to your domain, a look-alike phishing site &lt;strong&gt;can't&lt;/strong&gt; get a valid signature. That's the main security win over passwords and one-time codes.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Password&lt;/th&gt;
&lt;th&gt;Passkey&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Secret stored on server&lt;/td&gt;
&lt;td&gt;Hash of a shared secret&lt;/td&gt;
&lt;td&gt;Public key only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Phishable&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Resistant (origin-bound)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reusable across sites&lt;/td&gt;
&lt;td&gt;Often (badly)&lt;/td&gt;
&lt;td&gt;No, unique per site&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;User effort&lt;/td&gt;
&lt;td&gt;Type/remember&lt;/td&gt;
&lt;td&gt;Biometric or device PIN&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Terminology Cheat Sheet
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Relying Party (RP):&lt;/strong&gt; your site.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RP ID:&lt;/strong&gt; usually your domain, e.g., &lt;code&gt;example.com&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authenticator:&lt;/strong&gt; the device or credential manager holding the private key.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Challenge:&lt;/strong&gt; random bytes your server generates &lt;em&gt;per ceremony&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Credential ID:&lt;/strong&gt; identifier you store and use to look up the public key.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 1: Registration (Creating a Passkey)
&lt;/h2&gt;

&lt;p&gt;Your server first generates options, including a fresh random challenge. Then the browser calls &lt;code&gt;navigator.credentials.create()&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// optionsFromServer is JSON your server created.&lt;/span&gt;
&lt;span class="c1"&gt;// Binary fields (challenge, user.id) are base64url strings in transit.&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;b64urlToBuf&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;pad&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;=&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;repeat&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="mi"&gt;4&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;%&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="o"&gt;%&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;b64&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;s&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nx"&gt;pad&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/-/g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;+&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/_/g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nb"&gt;Uint8Array&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="k"&gt;from&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;atob&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;b64&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;c&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;charCodeAt&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)).&lt;/span&gt;&lt;span class="nx"&gt;buffer&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;bufToB64url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;buf&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;
  &lt;span class="nf"&gt;btoa&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;fromCharCode&lt;/span&gt;&lt;span class="p"&gt;(...&lt;/span&gt;&lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Uint8Array&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;buf&lt;/span&gt;&lt;span class="p"&gt;)))&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/&lt;/span&gt;&lt;span class="se"&gt;\+&lt;/span&gt;&lt;span class="sr"&gt;/g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;-&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/&lt;/span&gt;&lt;span class="se"&gt;\/&lt;/span&gt;&lt;span class="sr"&gt;/g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;_&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/=+$/&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;''&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;registerPasskey&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;optionsFromServer&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/webauthn/register/options&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;credentials&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;include&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}).&lt;/span&gt;&lt;span class="nf"&gt;then&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;());&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;publicKey&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;challenge&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;b64urlToBuf&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;optionsFromServer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;challenge&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
    &lt;span class="na"&gt;rp&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Example App&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;example.com&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;user&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;b64urlToBuf&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;optionsFromServer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="c1"&gt;// opaque ID, NOT an email&lt;/span&gt;
      &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;optionsFromServer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;displayName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;optionsFromServer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;displayName&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;pubKeyCredParams&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;public-key&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;alg&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;7&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;   &lt;span class="c1"&gt;// ES256&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;public-key&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;alg&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;257&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="c1"&gt;// RS256&lt;/span&gt;
    &lt;span class="p"&gt;],&lt;/span&gt;
    &lt;span class="na"&gt;authenticatorSelection&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;residentKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;preferred&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;      &lt;span class="c1"&gt;// discoverable credential (a true passkey)&lt;/span&gt;
      &lt;span class="na"&gt;userVerification&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;preferred&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;timeout&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;60000&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;};&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;cred&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;credentials&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;publicKey&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="c1"&gt;// Send the result to the server for verification&lt;/span&gt;
  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/webauthn/register/verify&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Content-Type&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;credentials&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;include&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;cred&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;rawId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;cred&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;rawId&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
      &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;cred&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;type&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;response&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="na"&gt;clientDataJSON&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;cred&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;clientDataJSON&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
        &lt;span class="na"&gt;attestationObject&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;cred&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;attestationObject&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
      &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;}),&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Gotcha:&lt;/strong&gt; &lt;code&gt;user.id&lt;/code&gt; should be a stable, random, opaque identifier, &lt;em&gt;not&lt;/em&gt; an email address or anything personally identifying.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Authentication (Signing In)
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;signInWithPasskey&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;options&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/webauthn/login/options&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}).&lt;/span&gt;&lt;span class="nf"&gt;then&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;());&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;assertion&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;credentials&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;publicKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;challenge&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;b64urlToBuf&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;options&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;challenge&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
      &lt;span class="na"&gt;rpId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;example.com&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;userVerification&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;preferred&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="c1"&gt;// Leave allowCredentials empty to let the user pick a discoverable passkey&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/webauthn/login/verify&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Content-Type&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;rawId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;rawId&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
      &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;type&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;response&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="na"&gt;clientDataJSON&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;clientDataJSON&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
        &lt;span class="na"&gt;authenticatorData&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;authenticatorData&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
        &lt;span class="na"&gt;signature&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;signature&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
        &lt;span class="na"&gt;userHandle&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;userHandle&lt;/span&gt;
          &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="nf"&gt;bufToB64url&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;assertion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;userHandle&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
          &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;}),&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;ok&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Bonus: Autofill UI (Conditional Mediation)
&lt;/h3&gt;

&lt;p&gt;You can show passkeys in the browser's autofill dropdown so users don't need a separate button:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;input&lt;/span&gt; &lt;span class="na"&gt;type=&lt;/span&gt;&lt;span class="s"&gt;"text"&lt;/span&gt; &lt;span class="na"&gt;name=&lt;/span&gt;&lt;span class="s"&gt;"username"&lt;/span&gt; &lt;span class="na"&gt;autocomplete=&lt;/span&gt;&lt;span class="s"&gt;"username webauthn"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;PublicKeyCredential&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt;
  &lt;span class="nx"&gt;PublicKeyCredential&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;isConditionalMediationAvailable&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt;
  &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;PublicKeyCredential&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isConditionalMediationAvailable&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// Call navigator.credentials.get({ publicKey, mediation: 'conditional' })&lt;/span&gt;
  &lt;span class="c1"&gt;// on page load, then verify the result as usual.&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 3: What Your Server MUST Verify
&lt;/h2&gt;

&lt;p&gt;This is where implementations go wrong. For each ceremony the server must check at least:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Challenge&lt;/strong&gt; matches the one it issued, is single-use, and hasn't expired&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Origin&lt;/strong&gt; in &lt;code&gt;clientDataJSON&lt;/code&gt; matches your expected origin&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RP ID hash&lt;/strong&gt; in the authenticator data matches your RP ID&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Type&lt;/strong&gt; is &lt;code&gt;webauthn.create&lt;/code&gt; or &lt;code&gt;webauthn.get&lt;/code&gt; as appropriate&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Signature&lt;/strong&gt; is valid against the stored public key (on sign-in)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User verification / presence flags&lt;/strong&gt; meet your policy&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Signature counter&lt;/strong&gt; behavior, handled sensibly (some passkey providers always return 0)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then store: &lt;code&gt;credentialId&lt;/code&gt;, &lt;code&gt;publicKey&lt;/code&gt;, &lt;code&gt;userId&lt;/code&gt;, &lt;code&gt;transports&lt;/code&gt;, and &lt;code&gt;createdAt&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Don't hand-roll this. Use a well-maintained library such as &lt;strong&gt;SimpleWebAuthn&lt;/strong&gt; for Node.js or an equivalent for your language, and check its docs for the current API since options shapes change between major versions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Pitfalls
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Wrong RP ID or origin.&lt;/strong&gt; Passkeys silently fail if the RP ID isn't your domain or a registrable suffix of it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reusing challenges.&lt;/strong&gt; Always random, always single-use.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No recovery path.&lt;/strong&gt; Offer multiple passkeys per account and a secure recovery flow. Locking users out is a real risk.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Removing every fallback too early.&lt;/strong&gt; Roll out passkeys as an &lt;em&gt;option&lt;/em&gt; first, then measure adoption.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Using email as &lt;code&gt;user.id&lt;/code&gt;.&lt;/strong&gt; Use an opaque random ID.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HTTP in production.&lt;/strong&gt; WebAuthn requires a secure context (HTTPS; &lt;code&gt;localhost&lt;/code&gt; works for development).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ignoring account recovery security.&lt;/strong&gt; Attackers will target the weakest path. A passkey is only as strong as your reset flow.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Rollout Strategy That Works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Add "Create a passkey" after a successful password login.&lt;/li&gt;
&lt;li&gt;Support passkey sign-in alongside existing methods.&lt;/li&gt;
&lt;li&gt;Track adoption and failures.&lt;/li&gt;
&lt;li&gt;Gradually encourage passkeys, and retire password-only paths later if your risk model allows.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Wrapping Up
&lt;/h2&gt;

&lt;p&gt;Passkeys remove the shared secret from the equation, making phishing and credential stuffing much less effective. The browser API is small. The hard parts are &lt;strong&gt;correct server verification&lt;/strong&gt; and &lt;strong&gt;thoughtful recovery flows&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;If you've shipped passkeys, what tripped you up? Share it in the comments. I'd love to build a list of real-world gotchas.&lt;/p&gt;

&lt;h2&gt;
  
  
  Resources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;MDN Web Docs: Web Authentication API&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devops</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Git Is Not a Backup: Cloud Backup vs Local Backup for Developers</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Fri, 23 Oct 2026 11:10:06 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/git-is-not-a-backup-cloud-backup-vs-local-backup-for-developers-51ip</link>
      <guid>https://dev.to/zianetworksinsight/git-is-not-a-backup-cloud-backup-vs-local-backup-for-developers-51ip</guid>
      <description>&lt;p&gt;A few years ago I would have told you my code was "backed up" because it was on GitHub. Then I started thinking about everything that isn't in the repo: the &lt;code&gt;.env&lt;/code&gt; files, the local database, the client assets, the notes, and the config that only exists on my laptop.&lt;/p&gt;

&lt;p&gt;If you freelance, run a small agency, or look after IT for a small business, the &lt;strong&gt;cloud backup vs. local backup&lt;/strong&gt; question is worth ten minutes of your time. Here's a developer-friendly way to think about it, plus a setup you can copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, a myth: Git is not a backup
&lt;/h2&gt;

&lt;p&gt;Git is great at history and collaboration. It is a poor backup for the whole machine because:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Untracked and ignored files (&lt;code&gt;.env&lt;/code&gt;, local databases, and build artefacts you can't regenerate) aren't in it.&lt;/li&gt;
&lt;li&gt;A force-push or deleted remote can wipe history.&lt;/li&gt;
&lt;li&gt;If your remote account is locked or compromised, your copy is only as safe as that account.&lt;/li&gt;
&lt;li&gt;Your documents, client files, and system config aren't in any repo.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep using Git. Just don't call it your backup plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Local vs cloud in one minute
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Local backup&lt;/strong&gt; copies data to hardware you control: an external SSD, a NAS, another machine.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;✅ Fast restores, works offline, no monthly storage bill&lt;/li&gt;
&lt;li&gt;❌ Same building as the original, so theft, fire, flood, or a power surge can take both&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cloud backup&lt;/strong&gt; sends encrypted copies to a provider's storage.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;✅ Offsite, automatic, scalable&lt;/li&gt;
&lt;li&gt;❌ Slow for huge restores, ongoing cost, depends on credentials and the vendor&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Neither is enough alone. They cover different failures.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 3-2-1 rule
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;3&lt;/strong&gt; copies of your data (the original plus two backups)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2&lt;/strong&gt; types of storage (local disc plus cloud, for example)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;1&lt;/strong&gt; copy offsite&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A simple dev workstation setup
&lt;/h2&gt;

&lt;p&gt;Here's a minimal version using tools that are already on most Linux and macOS machines, plus &lt;code&gt;rclone&lt;/code&gt; for cloud storage. Adjust paths to suit.&lt;/p&gt;

&lt;h3&gt;
  
  
  Local: versioned snapshots with rsync
&lt;/h3&gt;

&lt;p&gt;This keeps dated snapshots, using hard links so unchanged files don't take extra space.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;#!/usr/bin/env bash&lt;/span&gt;
&lt;span class="nb"&gt;set&lt;/span&gt; &lt;span class="nt"&gt;-euo&lt;/span&gt; pipefail

&lt;span class="nv"&gt;SRC&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$HOME&lt;/span&gt;&lt;span class="s2"&gt;/projects/"&lt;/span&gt;
&lt;span class="nv"&gt;DEST&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"/mnt/backup/projects"&lt;/span&gt;
&lt;span class="nv"&gt;TODAY&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt; +%F&lt;span class="si"&gt;)&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;

&lt;span class="nb"&gt;mkdir&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$DEST&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;

rsync &lt;span class="nt"&gt;-a&lt;/span&gt; &lt;span class="nt"&gt;--delete&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--exclude&lt;/span&gt; &lt;span class="s1"&gt;'node_modules/'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--exclude&lt;/span&gt; &lt;span class="s1"&gt;'.cache/'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--link-dest&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$DEST&lt;/span&gt;&lt;span class="s2"&gt;/latest"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$SRC&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$DEST&lt;/span&gt;&lt;span class="s2"&gt;/&lt;/span&gt;&lt;span class="nv"&gt;$TODAY&lt;/span&gt;&lt;span class="s2"&gt;/"&lt;/span&gt;

&lt;span class="nb"&gt;ln&lt;/span&gt; &lt;span class="nt"&gt;-sfn&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$DEST&lt;/span&gt;&lt;span class="s2"&gt;/&lt;/span&gt;&lt;span class="nv"&gt;$TODAY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$DEST&lt;/span&gt;&lt;span class="s2"&gt;/latest"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Skipping &lt;code&gt;node_modules&lt;/code&gt; saves a lot of space because you can rebuild it from your lockfile. Don't exclude anything you can't regenerate.&lt;/p&gt;

&lt;h3&gt;
  
  
  Offsite: encrypted copy with rclone
&lt;/h3&gt;

&lt;p&gt;Configure a remote once with &lt;code&gt;rclone config&lt;/code&gt; (many providers are supported, and you can layer a &lt;code&gt;crypt&lt;/code&gt; remote on top for client-side encryption). Then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;rclone copy &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$HOME&lt;/span&gt;&lt;span class="s2"&gt;/projects"&lt;/span&gt; remote:backups/projects &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--exclude&lt;/span&gt; &lt;span class="s1"&gt;'node_modules/**'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--exclude&lt;/span&gt; &lt;span class="s1"&gt;'.cache/**'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--progress&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I used &lt;code&gt;copy&lt;/code&gt; rather than &lt;code&gt;sync&lt;/code&gt; on purpose. &lt;code&gt;sync&lt;/code&gt; mirrors deletions, so an accidental delete or a ransomware encryption could propagate to the cloud. If you do use &lt;code&gt;sync&lt;/code&gt;, turn on versioning or object lock at the provider, or use &lt;code&gt;--backup-dir&lt;/code&gt; so overwritten and deleted files are kept.&lt;/p&gt;

&lt;h3&gt;
  
  
  Schedule it
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;crontab &lt;span class="nt"&gt;-e&lt;/span&gt;
&lt;span class="c"&gt;# Local snapshot at 1:30 AM, cloud copy at 2:30 AM&lt;/span&gt;
30 1 &lt;span class="k"&gt;*&lt;/span&gt; &lt;span class="k"&gt;*&lt;/span&gt; &lt;span class="k"&gt;*&lt;/span&gt; /home/you/bin/local-backup.sh &lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt; /home/you/backup.log 2&amp;gt;&amp;amp;1
30 2 &lt;span class="k"&gt;*&lt;/span&gt; &lt;span class="k"&gt;*&lt;/span&gt; &lt;span class="k"&gt;*&lt;/span&gt; rclone copy /home/you/projects remote:backups/projects &lt;span class="nt"&gt;--exclude&lt;/span&gt; &lt;span class="s1"&gt;'node_modules/**'&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt; /home/you/backup.log 2&amp;gt;&amp;amp;1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then add something that tells you when it fails: a notification, an email, or a health-check ping. Silent failure is how people discover three months later that nothing has run.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part everyone skips: test the restore
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Restore a folder from the latest local snapshot to a scratch location&lt;/span&gt;
&lt;span class="nb"&gt;mkdir&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt; /tmp/restore-test
rsync &lt;span class="nt"&gt;-a&lt;/span&gt; /mnt/backup/projects/latest/my-important-project/ /tmp/restore-test/

&lt;span class="c"&gt;# Try to open and run it&lt;/span&gt;
&lt;span class="nb"&gt;cd&lt;/span&gt; /tmp/restore-test &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;ls&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do the same from the cloud copy at least twice a year, and time it. That number is your real recovery time, and it's usually longer than you'd guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things worth thinking about if you're a small business or work in a region like northern New Mexico
&lt;/h2&gt;

&lt;p&gt;I live with a few real-world hazards in mind when advising local businesses: summer storms and power surges, wildfire season, dry dust, and older buildings. They all argue for the same thing: keep at least one copy somewhere other than your office, and put surge protection on anything that stores data.&lt;/p&gt;

&lt;p&gt;If you handle client health or financial data, check which regulations apply and whether your backup provider meets them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Code is in Git, and Git is &lt;strong&gt;not&lt;/strong&gt; my only backup.&lt;/li&gt;
&lt;li&gt;[ ] I have a local snapshot with some version history.&lt;/li&gt;
&lt;li&gt;[ ] I have an encrypted offsite copy&lt;/li&gt;
&lt;li&gt;[ ] Deleted files can't instantly vanish from every copy.&lt;/li&gt;
&lt;li&gt;[ ] Secrets are stored in a password manager, not just a local``&lt;/li&gt;
&lt;li&gt;[ ] Backup failures notify me.&lt;/li&gt;
&lt;li&gt;[ ] I've restored from backup in the last six months.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Wrap-up
&lt;/h2&gt;

&lt;p&gt;For the &lt;strong&gt;cloud backup vs local backup&lt;/strong&gt; question, the practical answer is both. Local for speed, cloud for survival, and a restore test to prove it works.&lt;/p&gt;

&lt;p&gt;What's in your backup setup? Let me know what tools you use in the comments.&lt;/p&gt;

</description>
      <category>backup</category>
      <category>devops</category>
      <category>linux</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Passkeys vs. Passwords: What Small Business Teams Should Actually Do</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Thu, 22 Oct 2026 06:47:18 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/passkeys-vs-passwords-what-small-business-teams-should-actually-do-2lpb</link>
      <guid>https://dev.to/zianetworksinsight/passkeys-vs-passwords-what-small-business-teams-should-actually-do-2lpb</guid>
      <description>&lt;p&gt;Most small businesses have no security team. They have a handful of people, fifty-ish logins, and one person who happens to be "good with computers." If that person is you, this post is for you.&lt;/p&gt;

&lt;p&gt;The &lt;strong&gt;passkeys vs. passwords&lt;/strong&gt; debate has moved past theory. Passkeys are supported across Apple, Google, and Microsoft platforms, and many major services now offer them. The real question is how to adopt them without breaking your team's workflow.&lt;/p&gt;

&lt;p&gt;I'm writing this on behalf of &lt;strong&gt;ZIA Networks&lt;/strong&gt;, where we help small businesses make practical security decisions, so I'll keep it grounded.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why passwords keep failing small teams
&lt;/h2&gt;

&lt;p&gt;Passwords have three problems that training only partly fixes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Reuse.&lt;/strong&gt; One leaked password from an unrelated site can unlock a business account.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Phishing.&lt;/strong&gt; A convincing fake login page can capture a typed password in seconds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Overhead.&lt;/strong&gt; Resets, lockouts, and shared spreadsheets cost time every week.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The weakness is structural: a password is a shared secret that can be typed anywhere, real or fake.&lt;/p&gt;

&lt;h2&gt;
  
  
  How passkeys work (the short version)
&lt;/h2&gt;

&lt;p&gt;Passkeys are built on the &lt;strong&gt;WebAuthn&lt;/strong&gt; and &lt;strong&gt;FIDO2&lt;/strong&gt; standards and use public-key cryptography.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;During registration, the user's device creates a key pair.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;private key&lt;/strong&gt; stays on the device (or in a synced credential manager).&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;public key&lt;/strong&gt; is stored by the service.&lt;/li&gt;
&lt;li&gt;At sign-in, the service sends a challenge; the device signs it after the user verifies with a biometric or PIN, and the service checks the signature.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Two properties matter for security:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The credential is &lt;strong&gt;bound to the site's domain&lt;/strong&gt; (the relying party ID), so a lookalike domain can't use it.&lt;/li&gt;
&lt;li&gt;A server breach exposes &lt;strong&gt;public keys only&lt;/strong&gt;, which are useless to an attacker.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What registration looks like in code
&lt;/h2&gt;

&lt;p&gt;If you build or maintain a web app for your business, here is a simplified browser-side registration call. The options come from your server, and the &lt;code&gt;challenge&lt;/code&gt; must be random and single-use.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;credential&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nb"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;credentials&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;publicKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;challenge&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;challengeFromServer&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;        &lt;span class="c1"&gt;// ArrayBuffer, generated server-side&lt;/span&gt;
    &lt;span class="na"&gt;rp&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Example Co&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;example.com&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;user&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;userIdBytes&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;                     &lt;span class="c1"&gt;// stable, opaque user handle&lt;/span&gt;
      &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;dana@example.com&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;displayName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Dana&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;pubKeyCredParams&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;public-key&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;alg&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;7&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;     &lt;span class="c1"&gt;// ES256&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;public-key&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;alg&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;257&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;   &lt;span class="c1"&gt;// RS256&lt;/span&gt;
    &lt;span class="p"&gt;],&lt;/span&gt;
    &lt;span class="na"&gt;authenticatorSelection&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;residentKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;required&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;             &lt;span class="c1"&gt;// creates a discoverable passkey&lt;/span&gt;
      &lt;span class="na"&gt;userVerification&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;preferred&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;},&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="c1"&gt;// Send the result to your server, which must verify it and store the public key.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One important note: &lt;strong&gt;don't write the server-side verification yourself.&lt;/strong&gt; Use a well-maintained library (SimpleWebAuthn is a popular option for Node.js) and review its documentation carefully. Cryptographic code is easy to get subtly wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where passkeys win
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Area&lt;/th&gt;
&lt;th&gt;Passwords&lt;/th&gt;
&lt;th&gt;Passkeys&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Phishing resistance&lt;/td&gt;
&lt;td&gt;Weak&lt;/td&gt;
&lt;td&gt;Strong (domain-bound)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Breach impact&lt;/td&gt;
&lt;td&gt;Reusable secrets can leak&lt;/td&gt;
&lt;td&gt;Only public keys stored&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reuse and guessing&lt;/td&gt;
&lt;td&gt;Common problem&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sign-in speed&lt;/td&gt;
&lt;td&gt;Typing and resets&lt;/td&gt;
&lt;td&gt;Touch or glance&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Where passkeys fall short
&lt;/h2&gt;

&lt;p&gt;I'd rather be honest than hype this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Not universal.&lt;/strong&gt; Older software and niche tools may only support passwords, so you'll run both for a while.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recovery needs design.&lt;/strong&gt; Synced passkeys (iCloud Keychain, Google Password Manager) make device loss easier to handle, but that account becomes a high-value target. Protect it well.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shared accounts are awkward.&lt;/strong&gt; Passkeys are built around individuals. Shared logins are better handled with a business password manager or separate user seats.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Adoption takes a little training.&lt;/strong&gt; A short walkthrough prevents confusion.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A practical rollout plan
&lt;/h2&gt;

&lt;p&gt;You don't need a big-bang migration:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Inventory your accounts&lt;/strong&gt; and mark which ones would hurt most to lose: email, cloud storage, accounting, and banking.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enable passkeys on those first&lt;/strong&gt;, and test sign-in before removing anything else.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a business password manager&lt;/strong&gt; for tools without passkey support, with long, unique passwords.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep MFA on&lt;/strong&gt; every account that still uses a password.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write a recovery plan&lt;/strong&gt;: who helps when a phone is lost, and where recovery info is stored.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Brief the team&lt;/strong&gt; in 15 minutes. Keep it simple.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review quarterly&lt;/strong&gt;, since more services add support all the time.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Takeaway
&lt;/h2&gt;

&lt;p&gt;Where they're supported, passkeys are the safer choice: they resist phishing, leave nothing reusable in a breach, and make sign-in faster. Passwords still have a place as a backup for tools that haven't caught up.&lt;/p&gt;

&lt;p&gt;If you'd like help deciding which accounts to move first or setting up recovery without disrupting your team, &lt;strong&gt;ZIA Networks&lt;/strong&gt; can walk you through it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Discussion
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Have you rolled out passkeys for a team or a product yet?&lt;/li&gt;
&lt;li&gt;Which tools in your stack still don't support them?&lt;/li&gt;
&lt;li&gt;How do you handle shared accounts and recovery?&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>authentication</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>HIPAA Security Rule Updates 2026: A Developer's Guide for Santa Fe Clinics</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Mon, 12 Oct 2026 07:04:28 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/hipaa-security-rule-updates-2026-a-developers-guide-for-santa-fe-clinics-282k</link>
      <guid>https://dev.to/zianetworksinsight/hipaa-security-rule-updates-2026-a-developers-guide-for-santa-fe-clinics-282k</guid>
      <description>&lt;p&gt;If you build or maintain systems for healthcare clinics, the &lt;strong&gt;HIPAA Security Rule updates 2026&lt;/strong&gt; probably landed in your backlog as a vague "we need to be ready". Here is what is actually happening and what to do about it, from the team at &lt;strong&gt;ZIA Networks&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The big security rule overhaul is &lt;strong&gt;still only proposed&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;The current rule &lt;strong&gt;stays enforceable&lt;/strong&gt; until a final rule replaces it.&lt;/li&gt;
&lt;li&gt;The proposal points to encryption, MFA, network segmentation, and documentation. Build for those now.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where the rule stands
&lt;/h2&gt;

&lt;p&gt;HHS's Office for Civil Rights published the proposed update on January 6, 2025. A final rule was targeted for May 2026, but HHS has delayed final action until at least July 2027.&lt;/p&gt;

&lt;p&gt;The existing security rule remains fully in effect and enforceable until a final rule replaces it. And penalties are real: after the 2026 inflation adjustment, they run from $145 to over $73,000 per violation, with annual caps above $2.1 million per category.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is already mandatory in 2026
&lt;/h2&gt;

&lt;p&gt;The updated Notice of Privacy Practices requirement, tied to the 42 CFR Part 2 final rule, became mandatory on February 16, 2026. If your clinic's patient portal or website links to an old notice, update it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the proposal signals for your stack
&lt;/h2&gt;

&lt;p&gt;The proposal would require specific technical standards such as encryption, multifactor authentication, and network segmentation. It would also convert several "addressable" safeguards into "required" controls. And it would require written documentation for all policies, procedures, plans, and analyses.&lt;/p&gt;

&lt;p&gt;In engineering terms, that looks like this:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Proposed direction&lt;/th&gt;
&lt;th&gt;What to build or check&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Encryption&lt;/td&gt;
&lt;td&gt;TLS in transit, encrypted storage and backups, encrypted endpoints&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MFA&lt;/td&gt;
&lt;td&gt;Enforce on email, EHR, VPN, admin consoles, cloud dashboards&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Network segmentation&lt;/td&gt;
&lt;td&gt;VLANs or separate subnets for clinical systems, guest Wi-Fi isolated&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Asset inventory&lt;/td&gt;
&lt;td&gt;Auto-discovered list of devices, servers, and SaaS tools touching ePHI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Documentation&lt;/td&gt;
&lt;td&gt;Policies, runbooks, and risk analysis kept in version control or a managed wiki&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  A starter checklist
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;hipaa_readiness_2026&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;risk_analysis&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;documented, reviewed at least annually&lt;/span&gt;
  &lt;span class="na"&gt;mfa&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;enabled on all remote and admin access&lt;/span&gt;
  &lt;span class="na"&gt;encryption&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;at_rest&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
    &lt;span class="na"&gt;in_transit&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
    &lt;span class="na"&gt;backups&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
  &lt;span class="na"&gt;asset_inventory&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;maintained and current&lt;/span&gt;
  &lt;span class="na"&gt;network_segmentation&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;clinical vs guest vs office&lt;/span&gt;
  &lt;span class="na"&gt;backups&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;tested restores, not just scheduled jobs&lt;/span&gt;
  &lt;span class="na"&gt;incident_response_plan&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;written and rehearsed&lt;/span&gt;
  &lt;span class="na"&gt;business_associates&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;agreements reviewed&lt;/span&gt;
  &lt;span class="na"&gt;staff_training&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;phishing and data handling&lt;/span&gt;
  &lt;span class="na"&gt;nm_breach_rules&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;confirmed with legal counsel&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Inadequate risk analysis is the most common security rule deficiency OCR cites in enforcement investigations. If you only do one thing from this list, do that one, and write it down. &lt;/p&gt;

&lt;h2&gt;
  
  
  Why not wait until 2027?
&lt;/h2&gt;

&lt;p&gt;The delay gives organisations more time to build asset inventories, encryption coverage, and MFA rollouts. Ransomware and phishing won't wait for a final rule, and every item above reduces your breach risk today. &lt;/p&gt;

&lt;h2&gt;
  
  
  How ZIA Networks can help
&lt;/h2&gt;

&lt;p&gt;Small clinics rarely have a dedicated security team. ZIA Networks helps review network and security setups, spot compliance gaps, and prioritise fixes in a practical order.&lt;/p&gt;

&lt;p&gt;Have questions about &lt;strong&gt;HIPAA Security Rule updates 2026&lt;/strong&gt; or your clinic's setup? Drop them in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclaimer: This post is general information, not legal advice. Consult a qualified HIPAA compliance professional or healthcare attorney for guidance specific to your clinic.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>devops</category>
    </item>
    <item>
      <title>Your Backups Probably Haven't Been Tested: The 3-2-1 Rule and a Simple Restore Check</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Thu, 08 Oct 2026 06:47:03 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/your-backups-probably-havent-been-tested-the-3-2-1-rule-and-a-simple-restore-check-3c70</link>
      <guid>https://dev.to/zianetworksinsight/your-backups-probably-havent-been-tested-the-3-2-1-rule-and-a-simple-restore-check-3c70</guid>
      <description>&lt;p&gt;Almost everyone has backups. Far fewer people have ever &lt;em&gt;restored&lt;/em&gt; one.&lt;/p&gt;

&lt;p&gt;That gap is where backup plans fail. The job ran every night, the dashboard showed green, and then the day came when someone needed the data and the files were empty, corrupted, or missing the one folder that mattered.&lt;/p&gt;

&lt;p&gt;This post covers the 3-2-1 rule, a few ways backups quietly fail, and a small script you can adapt to check that your restores actually work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 3-2-1 rule
&lt;/h2&gt;

&lt;p&gt;It's an old rule because it holds up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;3&lt;/strong&gt; copies of your data (the live copy plus two backups)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2&lt;/strong&gt; different types of storage (for example, a local disc and the cloud)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;1&lt;/strong&gt; copy off-site, so a fire, theft, or flood can't take everything&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A common modern addition is that at least one copy should be &lt;strong&gt;immutable or offline&lt;/strong&gt;. Ransomware can encrypt anything it can reach, including a backup drive mounted on the same network.&lt;/p&gt;

&lt;h2&gt;
  
  
  How backups fail without anyone noticing
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The job runs but backs up the wrong thing.&lt;/strong&gt; A moved folder or a new drive that was never added to the selection.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The backup is corrupt.&lt;/strong&gt; Silent errors on disk or in transit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Credentials expired.&lt;/strong&gt; The cloud target rejects uploads and the alert goes to an unused inbox.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ransomware reaches the backup.&lt;/strong&gt; It's writable from the same machine, so it gets encrypted too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nobody knows the restore procedure.&lt;/strong&gt; The data exists, but the one person who knew how to recover it left.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recovery is too slow.&lt;/strong&gt; A full restore takes three days and the business can't wait that long.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most of these only show up when you try a restore.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple restore check
&lt;/h2&gt;

&lt;p&gt;The idea: restore the latest backup into a scratch folder, pick a few random files from the live data, and compare checksums against the restored copies.&lt;/p&gt;

&lt;p&gt;Adjust the paths and the restore command for your tool. The example assumes a tool like &lt;code&gt;restic&lt;/code&gt; that restores files under their original path inside the target folder.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;#!/usr/bin/env bash&lt;/span&gt;
&lt;span class="nb"&gt;set&lt;/span&gt; &lt;span class="nt"&gt;-euo&lt;/span&gt; pipefail

&lt;span class="nv"&gt;SOURCE_DIR&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"/srv/company-data"&lt;/span&gt;
&lt;span class="nv"&gt;RESTORE_DIR&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"/tmp/restore-test"&lt;/span&gt;
&lt;span class="nv"&gt;SAMPLE_SIZE&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;5

&lt;span class="nb"&gt;rm&lt;/span&gt; &lt;span class="nt"&gt;-rf&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$RESTORE_DIR&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
&lt;span class="nb"&gt;mkdir&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$RESTORE_DIR&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;

&lt;span class="c"&gt;# 1. Restore the latest backup into a scratch folder.&lt;/span&gt;
&lt;span class="c"&gt;#    Replace this line with your backup tool's restore command.&lt;/span&gt;
&lt;span class="c"&gt;# restic restore latest --target "$RESTORE_DIR"&lt;/span&gt;

&lt;span class="c"&gt;# 2. Pick random files that haven't changed in the last day,&lt;/span&gt;
&lt;span class="c"&gt;#    so recent edits don't cause false alarms.&lt;/span&gt;
&lt;span class="nb"&gt;mapfile&lt;/span&gt; &lt;span class="nt"&gt;-t&lt;/span&gt; FILES &amp;lt; &amp;lt;&lt;span class="o"&gt;(&lt;/span&gt;find &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$SOURCE_DIR&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="nt"&gt;-type&lt;/span&gt; f &lt;span class="nt"&gt;-mtime&lt;/span&gt; +1 | &lt;span class="nb"&gt;shuf&lt;/span&gt; &lt;span class="nt"&gt;-n&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$SAMPLE_SIZE&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="k"&gt;${#&lt;/span&gt;&lt;span class="nv"&gt;FILES&lt;/span&gt;&lt;span class="p"&gt;[@]&lt;/span&gt;&lt;span class="k"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="nt"&gt;-eq&lt;/span&gt; 0 &lt;span class="o"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then
  &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"FAIL: no sample files found in &lt;/span&gt;&lt;span class="nv"&gt;$SOURCE_DIR&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
  &lt;span class="nb"&gt;exit &lt;/span&gt;1
&lt;span class="k"&gt;fi

&lt;/span&gt;&lt;span class="nv"&gt;failures&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0

&lt;span class="k"&gt;for &lt;/span&gt;f &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="k"&gt;${&lt;/span&gt;&lt;span class="nv"&gt;FILES&lt;/span&gt;&lt;span class="p"&gt;[@]&lt;/span&gt;&lt;span class="k"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do
  &lt;/span&gt;&lt;span class="nv"&gt;restored&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$RESTORE_DIR$f&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;

  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt; &lt;span class="nt"&gt;-f&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$restored&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then
    &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"MISSING: &lt;/span&gt;&lt;span class="nv"&gt;$f&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
    &lt;span class="nv"&gt;failures&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="k"&gt;$((&lt;/span&gt;failures &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="m"&gt;1&lt;/span&gt;&lt;span class="k"&gt;))&lt;/span&gt;
    &lt;span class="k"&gt;continue
  fi

  &lt;/span&gt;&lt;span class="nv"&gt;live_sum&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;sha256sum&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$f&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; | &lt;span class="nb"&gt;awk&lt;/span&gt; &lt;span class="s1"&gt;'{print $1}'&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;
  &lt;span class="nv"&gt;backup_sum&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;sha256sum&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$restored&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; | &lt;span class="nb"&gt;awk&lt;/span&gt; &lt;span class="s1"&gt;'{print $1}'&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;

  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$live_sum&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$backup_sum&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="o"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then
    &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"MISMATCH: &lt;/span&gt;&lt;span class="nv"&gt;$f&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
    &lt;span class="nv"&gt;failures&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="k"&gt;$((&lt;/span&gt;failures &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="m"&gt;1&lt;/span&gt;&lt;span class="k"&gt;))&lt;/span&gt;
  &lt;span class="k"&gt;else
    &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"OK: &lt;/span&gt;&lt;span class="nv"&gt;$f&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
  &lt;span class="k"&gt;fi
done

&lt;/span&gt;&lt;span class="nb"&gt;rm&lt;/span&gt; &lt;span class="nt"&gt;-rf&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$RESTORE_DIR&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;

&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$failures&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="nt"&gt;-gt&lt;/span&gt; 0 &lt;span class="o"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then
  &lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"Restore check FAILED (&lt;/span&gt;&lt;span class="nv"&gt;$failures&lt;/span&gt;&lt;span class="s2"&gt; problem(s))"&lt;/span&gt;
  &lt;span class="nb"&gt;exit &lt;/span&gt;1
&lt;span class="k"&gt;fi

&lt;/span&gt;&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"Restore check passed"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it from cron or a scheduled task, and send failures somewhere a human will actually see them, such as email, a chat channel, or a monitoring tool.&lt;/p&gt;

&lt;h3&gt;
  
  
  What this script doesn't prove
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;It checks a &lt;strong&gt;sample&lt;/strong&gt;, not every file.&lt;/li&gt;
&lt;li&gt;It doesn't test &lt;strong&gt;databases&lt;/strong&gt; or application consistency.&lt;/li&gt;
&lt;li&gt;It doesn't measure &lt;strong&gt;how long&lt;/strong&gt; a full restore takes.&lt;/li&gt;
&lt;li&gt;It doesn't cover &lt;strong&gt;bare-metal recovery&lt;/strong&gt; (rebuilding a whole machine).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Treat it as a smoke test, and still do a full recovery drill on a schedule.&lt;/p&gt;

&lt;h2&gt;
  
  
  A short checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] At least one copy is off-site.&lt;/li&gt;
&lt;li&gt;[ ] At least one copy can't be modified from your everyday network or accounts.&lt;/li&gt;
&lt;li&gt;[ ] Backup credentials are separate from daily-use admin accounts.&lt;/li&gt;
&lt;li&gt;[ ] Failure alerts go to a monitored channel.&lt;/li&gt;
&lt;li&gt;[ ] A sample restore runs automatically.&lt;/li&gt;
&lt;li&gt;[ ] A full restore drill happens at least a couple of times a year.&lt;/li&gt;
&lt;li&gt;[ ] The recovery steps are written down where someone else can find them.&lt;/li&gt;
&lt;li&gt;[ ] You know how long recovery takes and how much data you could lose&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where this shows up outside engineering
&lt;/h2&gt;

&lt;p&gt;Small teams without a dedicated ops person often assume "the cloud" is handling it. That's worth checking. Many SaaS tools have limited retention or no easy way to recover from accidental deletion, and "synced" isn't the same as "backed up".&lt;/p&gt;

&lt;p&gt;For a non-technical take you can share with a manager or client, see &lt;a href="https://www.zianetworks.net/blog/cloud-backup-vs-local-backup-which-is-better-for-small-businesses/" rel="noopener noreferrer"&gt;Cloud Backup vs Local Backup: Which Is Better for Small Businesses?&lt;/a&gt; and &lt;a href="https://www.zianetworks.net/blog/is-your-business-data-really-backed-up-what-most-business-owners-get-wrong/" rel="noopener noreferrer"&gt;Is Your Business Data Really Backed Up?&lt;/a&gt;. If you'd rather hand it off, &lt;a href="https://www.zianetworks.net/services/data-backup/" rel="noopener noreferrer"&gt;Zia Networks&lt;/a&gt; manages backups for small businesses in New Mexico.&lt;/p&gt;

&lt;h2&gt;
  
  
  Takeaway
&lt;/h2&gt;

&lt;p&gt;Don't trust a backup until you've restored from it. Automate a small check, alert a human on failure, and practice the full recovery before you need it.&lt;/p&gt;

&lt;p&gt;What does your restore testing look like today? Let me know in the comments.&lt;br&gt;
Before you publish&lt;br&gt;
Cover image: add one, since posts with images tend to get more clicks. A simple diagram of "3 copies, 2 media, 1 off-site" works.&lt;br&gt;
Set published: true only after you've previewed it.&lt;br&gt;
Don't set a canonical URL. This is original content, so it shouldn't point to your blog.&lt;br&gt;
Test the script on a throwaway folder before you tell readers it works. Make sure the restore command matches your tool.&lt;br&gt;
Tags: dev.to allows 4. Backup, security, DevOps, and beginners are all active.&lt;br&gt;
Tips&lt;br&gt;
Engage in comments. Replying to the first few comments helps the post get seen.&lt;br&gt;
Keep the promotion light. I kept it to one short paragraph near the end, since Dev.to readers dislike ads.&lt;br&gt;
Check link behaviour. Inspect the published page to see whether your links are followed.&lt;br&gt;
Add a series. A follow-up on offboarding access or patching would build your profile.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
    </item>
    <item>
      <title>How to Audit Microsoft 365 Mailboxes for Hidden Forwarding Rules</title>
      <dc:creator>ZIA Networks</dc:creator>
      <pubDate>Tue, 06 Oct 2026 07:52:31 +0000</pubDate>
      <link>https://dev.to/zianetworksinsight/how-to-audit-microsoft-365-mailboxes-for-hidden-forwarding-rules-1l</link>
      <guid>https://dev.to/zianetworksinsight/how-to-audit-microsoft-365-mailboxes-for-hidden-forwarding-rules-1l</guid>
      <description>&lt;p&gt;When a business mailbox gets compromised, resetting the password is only half the job. Attackers often leave behind &lt;strong&gt;forwarding rules&lt;/strong&gt; that quietly copy every new email to an outside address, even after the password has changed.&lt;/p&gt;

&lt;p&gt;This guide shows how to audit for those leftovers in Microsoft 365 using PowerShell.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters
&lt;/h2&gt;

&lt;p&gt;Common persistence tricks after account takeover:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Inbox rules that forward or redirect mail externally&lt;/li&gt;
&lt;li&gt;Mailbox-level forwarding (&lt;code&gt;ForwardingSmtpAddress&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Rules that move replies to hidden folders so the owner never sees them&lt;/li&gt;
&lt;li&gt;OAuth apps with mailbox permissions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you only reset the password, these can keep working.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prerequisites
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;An admin account with permission to read mailbox settings&lt;/li&gt;
&lt;li&gt;The Exchange Online module
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Install-Module&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;ExchangeOnlineManagement&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Scope&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;CurrentUser&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;Connect-ExchangeOnline&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;blockquote&gt;
&lt;p&gt;Test in a non-production tenant or on a single mailbox first, and follow your organization's change policy.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  1. Check mailbox-level forwarding
&lt;/h2&gt;

&lt;p&gt;This lists every mailbox that forwards mail somewhere else:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-ResultSize&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Unlimited&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Where-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardingSmtpAddress&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-ne&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$null&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardingAddress&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-ne&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$null&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;DisplayName&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;ForwardingSmtpAddress&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;ForwardingAddress&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;DeliverToMailboxAndForward&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Anything pointing to an external address you don't recognise deserves a closer look.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Check inbox rules for one mailbox
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-InboxRule&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="nx"&gt;yourdomain.com&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Where-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardAsAttachmentTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;RedirectTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Enabled&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;ForwardTo&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;ForwardAsAttachmentTo&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;RedirectTo&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Check inbox rules across all mailboxes
&lt;/h2&gt;

&lt;p&gt;For larger tenants, loop through mailboxes (this can take time):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-ResultSize&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Unlimited&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;ForEach-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;Get-InboxRule&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;UserPrincipalName&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="n"&gt;Where-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ForwardAsAttachmentTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-or&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;RedirectTo&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="n"&gt;Select-Object&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;@{&lt;/span&gt;&lt;span class="nx"&gt;n&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s1"&gt;'Mailbox'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="nx"&gt;e&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;MailboxOwnerId&lt;/span&gt;&lt;span class="p"&gt;}},&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Enabled&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;ForwardTo&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;RedirectTo&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Remove a suspicious rule
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Remove-InboxRule&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="nx"&gt;yourdomain.com&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Identity&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Rule Name"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To clear mailbox-level forwarding:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Set-Mailbox&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Identity&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="nx"&gt;yourdomain.com&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-ForwardingSmtpAddress&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$null&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-ForwardingAddress&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="bp"&gt;$null&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  5. Sign out active sessions
&lt;/h2&gt;

&lt;p&gt;Using the Microsoft Graph PowerShell module:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Connect-MgGraph&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Scopes&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"User.ReadWrite.All"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;Revoke-MgUserSignInSession&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-UserId&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="nx"&gt;yourdomain.com&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Post-incident checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Reset the password from a trusted device.&lt;/li&gt;
&lt;li&gt;[ ] Enforce MFA for the account.&lt;/li&gt;
&lt;li&gt;[ ] Remove unknown forwarding rules and mailbox forwarding.&lt;/li&gt;
&lt;li&gt;[ ] Revoke active sessions.&lt;/li&gt;
&lt;li&gt;[ ] Reviewed connected apps and consented to OAuth permissions&lt;/li&gt;
&lt;li&gt;[ ] Review recently sent items for fraud attempts.&lt;/li&gt;
&lt;li&gt;[ ] Check whether regulated data was exposed (e.g., HIPAA, PCI-DSS).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Prevent it next time
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Block automatic external forwarding with an outbound spam policy&lt;/li&gt;
&lt;li&gt;Turn on audit logging and alerts for new inbox rules.&lt;/li&gt;
&lt;li&gt;Require MFA for every user&lt;/li&gt;
&lt;li&gt;Run this audit on a schedule, not only after incidents.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;Hidden forwarding is one of the most common ways account takeovers continue silently. A short scheduled audit catches it early.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I'm Paul, founder of &lt;a href="https://www.zianetworks.net/" rel="noopener noreferrer"&gt;Zia Networks&lt;/a&gt;, a managed IT provider supporting small businesses across New Mexico. We also publish a free version for non-technical owners.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;What other persistence tricks have you seen after mailbox compromises? Share in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>cybersecurity</category>
      <category>software</category>
      <category>development</category>
    </item>
  </channel>
</rss>
