<?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: 早川徳一</title>
    <description>The latest articles on DEV Community by 早川徳一 (@nhayakawa).</description>
    <link>https://dev.to/nhayakawa</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%2F4172281%2F8c364c97-2524-4921-b029-9c373c08cbce.png</url>
      <title>DEV Community: 早川徳一</title>
      <link>https://dev.to/nhayakawa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nhayakawa"/>
    <language>en</language>
    <item>
      <title>We audited our PC and network — and found settings we only thought we had</title>
      <dc:creator>早川徳一</dc:creator>
      <pubDate>Wed, 14 Oct 2026 15:52:33 +0000</pubDate>
      <link>https://dev.to/exapolicy/we-audited-our-pc-and-network-and-found-settings-we-only-thought-we-had-4aff</link>
      <guid>https://dev.to/exapolicy/we-audited-our-pc-and-network-and-found-settings-we-only-thought-we-had-4aff</guid>
      <description>&lt;h2&gt;
  
  
  What this post is (and isn't)
&lt;/h2&gt;

&lt;p&gt;In &lt;a href="https://dev.to/exapolicy/list-what-you-need-to-protect-before-you-choose-your-defenses-1c5i"&gt;the previous post&lt;/a&gt;, we sorted what you need to protect onto five shelves. This post is a record of how we actually reviewed two of them — "devices" and "just in case" — in our own environment.&lt;/p&gt;

&lt;p&gt;In October 2026 we reviewed Exapolicy's environment in three layers. There is nothing special about it: it is built around the kind of broadband router you would find in any home. This post covers what we found, the measures we took, and the settings we only &lt;em&gt;thought&lt;/em&gt; we had.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What it includes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Development environment&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The PC we develop on, and the development server running on it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Office infrastructure&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The router, a NAS used for backup, and a printer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Devices on Wi-Fi&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;PCs that connect over Wi-Fi and are also used outside&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;ul&gt;
&lt;li&gt;This is a different layer from deciding what you send to an AI service (which is what our own product, Covenant, deals with).&lt;/li&gt;
&lt;li&gt;We checked everything with read-only commands and admin screens, and after each change we &lt;strong&gt;re-ran the same check&lt;/strong&gt; to confirm it.&lt;/li&gt;
&lt;li&gt;These are results from one environment. Others will differ.&lt;/li&gt;
&lt;li&gt;We don't name devices or describe settings or the network layout in detail. What we do write down are steps you can run on your own machine. Examples are for Windows.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  1. Why we looked
&lt;/h2&gt;

&lt;p&gt;Reports of personal data leaking from companies keep coming. As companies harden their side, individuals and very small businesses may become a more attractive target.&lt;/p&gt;

&lt;p&gt;We narrowed down what would actually hurt to two things:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What could hurt&lt;/th&gt;
&lt;th&gt;What an individual or small business can do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;Ransomware&lt;/strong&gt; (encrypts your files and demands payment)&lt;/td&gt;
&lt;td&gt;Keep a &lt;strong&gt;point you can roll back to&lt;/strong&gt;, even if the files are encrypted&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;DDoS&lt;/strong&gt; (floods a target with traffic)&lt;/td&gt;
&lt;td&gt;You can't stop one yourself. What you can do is &lt;strong&gt;make sure your own devices don't become part of the attack&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  2. What we found
&lt;/h2&gt;

&lt;p&gt;Here is the "before" state, by layer. None of it was one big mistake. It was &lt;strong&gt;a mix of factory defaults and permissions granted one at a time for convenience&lt;/strong&gt;. And in that state, the PC and the router &lt;strong&gt;worked perfectly well&lt;/strong&gt;. Working and being protected are two different things.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What we found&lt;/th&gt;
&lt;th&gt;What could happen&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Development&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;File shares were open to "Everyone"&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;If one password leaks, much of it can be rewritten from inside the LAN&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Development&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;A development server (a local LLM) was reachable from the whole LAN&lt;/strong&gt;, with no authentication&lt;/td&gt;
&lt;td&gt;Any device on the LAN could run, delete or replace models&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Development&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Remote access accepted connections from anywhere&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;More ways in&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Development&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Tamper Protection (which stops malware from turning off your antivirus) was off&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Ransomware typically tries to disable security software first&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Devices on Wi-Fi&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Inbound app permissions were also active on public networks&lt;/strong&gt; (the result of answering "Allow access?" over time)&lt;/td&gt;
&lt;td&gt;Someone on the same café Wi-Fi could reach those apps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Office infrastructure&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;The backup target was always connected and writable&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Ransomware encrypts the PC and the backup at the same time&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  3. Corrective actions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Development environment (PC)
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;th&gt;What we did&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Tamper Protection&lt;/td&gt;
&lt;td&gt;Ransomware tries to turn off antivirus first. Make sure it can't&lt;/td&gt;
&lt;td&gt;Turned it on&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Guest account&lt;/td&gt;
&lt;td&gt;A way in that anyone can use. If you don't use it, there's no reason to keep it&lt;/td&gt;
&lt;td&gt;Disabled it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;File share permissions&lt;/td&gt;
&lt;td&gt;Left at "Everyone", one leaked password is enough to rewrite a lot&lt;/td&gt;
&lt;td&gt;Limited to the owner and administrators&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Development server&lt;/td&gt;
&lt;td&gt;A server without authentication, open to the LAN, can be operated from any device on that network&lt;/td&gt;
&lt;td&gt;Made it reachable &lt;strong&gt;only from the PC itself&lt;/strong&gt;, and removed the inbound rule&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Remote access&lt;/td&gt;
&lt;td&gt;A convenient way in is a way in for an attacker too. Limit who can connect&lt;/td&gt;
&lt;td&gt;Allowed only from the office LAN and the VPN range. From outside, go through the VPN (no ports opened on the router)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Devices on Wi-Fi
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;th&gt;What we did&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Inbound app permissions&lt;/td&gt;
&lt;td&gt;On public Wi-Fi, strangers share your network. With the same permissions as at home or the office, they can reach you too&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Zero&lt;/strong&gt; on public networks; allowed only on the office LAN&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Office infrastructure (router)
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;th&gt;What we did&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Firmware updates&lt;/td&gt;
&lt;td&gt;The router is the entrance to the network. Old firmware keeps publicly known weaknesses open&lt;/td&gt;
&lt;td&gt;Set to update automatically&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Admin password and port forwarding&lt;/td&gt;
&lt;td&gt;These are the entrance settings themselves. Check that no unintended forwarding is left&lt;/td&gt;
&lt;td&gt;Checked&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;UPnP (lets devices open ports on their own)&lt;/td&gt;
&lt;td&gt;Devices can open a way in from outside without you knowing&lt;/td&gt;
&lt;td&gt;Turned off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WPS (push-button Wi-Fi pairing)&lt;/td&gt;
&lt;td&gt;Convenience in exchange for making it easier to join the Wi-Fi&lt;/td&gt;
&lt;td&gt;Turned off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Admin access from the internet side&lt;/td&gt;
&lt;td&gt;If the admin screen is visible from outside, it becomes a target&lt;/td&gt;
&lt;td&gt;Turned off&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Office infrastructure (backup)
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;th&gt;What we did&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Snapshots (point-in-time copies you can restore from)&lt;/td&gt;
&lt;td&gt;If files are encrypted or deleted, you can't get them back without a point to roll back to&lt;/td&gt;
&lt;td&gt;Scheduled daily snapshots, kept at daily, weekly and monthly intervals, so we &lt;strong&gt;can roll back a few months&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where snapshots can be deleted from&lt;/td&gt;
&lt;td&gt;If the PC can delete them, they go too when the PC is taken over&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;They can't be deleted from the PC side.&lt;/strong&gt; Even if the PC is taken over by ransomware, the rollback points remain&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Of everything we changed, we think that last row is the protection that matters most against ransomware.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Gaps in our settings
&lt;/h2&gt;

&lt;p&gt;This was the biggest lesson. In both cases, we found out only by &lt;strong&gt;re-running the same check after the change&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  4-1. Snapshots had stopped on one volume — about two years ago
&lt;/h3&gt;

&lt;p&gt;We believed the schedule existed. When we opened the snapshot list, the latest snapshot on one volume was about two years old. For that whole time, that volume &lt;strong&gt;had no point to roll back to&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;→ &lt;strong&gt;Don't check whether a schedule exists. Check the date of the latest snapshot.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  4-2. We removed a setting and rebooted — and the old setting kept running
&lt;/h3&gt;

&lt;p&gt;We removed the setting that exposed the development server to the LAN, and rebooted the PC. When we checked again, it was still reachable from the LAN.&lt;/p&gt;

&lt;p&gt;The cause was a &lt;strong&gt;process left running in the background&lt;/strong&gt;. It survived the reboot and kept the old setting. Only after ending that process from Task Manager and starting it again did the server listen on the PC alone.&lt;/p&gt;

&lt;p&gt;→ &lt;strong&gt;Don't check whether you rebooted. Check which address it is listening on right now.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Sync is not backup
&lt;/h2&gt;

&lt;p&gt;Syncing a folder to the cloud or to a NAS is convenient. But if ransomware encrypts your files, &lt;strong&gt;the encrypted files get synced too&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;When you look at a setup as protection against ransomware, check two things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Can you go back to an earlier point in time?&lt;/strong&gt; (Are versions kept?)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can those versions be deleted from the PC?&lt;/strong&gt; (Would they survive the PC being taken over?)&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  6. Let's check your own machine (Windows)
&lt;/h2&gt;

&lt;p&gt;All of these are &lt;strong&gt;read-only&lt;/strong&gt; commands. None of them change any setting. Run them in PowerShell as administrator.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is listening, and on which address
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-NetTCPConnection&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-State&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Listen&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;LocalAddress&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;LocalPort&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;OwningProcess&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;LocalPort&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A &lt;code&gt;LocalAddress&lt;/code&gt; of &lt;code&gt;0.0.0.0&lt;/code&gt; or &lt;code&gt;::&lt;/code&gt; means the service is &lt;strong&gt;reachable from outside the PC (the LAN)&lt;/strong&gt;. &lt;code&gt;127.0.0.1&lt;/code&gt; or &lt;code&gt;::1&lt;/code&gt; means the PC only. Match the &lt;code&gt;OwningProcess&lt;/code&gt; number to the PID on the &lt;strong&gt;Details&lt;/strong&gt; tab of Task Manager to see which app it is.&lt;/p&gt;

&lt;h3&gt;
  
  
  Inbound rules that are also active on public networks
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-NetFirewallRule&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Direction&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Inbound&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Enabled&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;True&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-Action&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;Allow&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;Profile&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-match&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s1"&gt;'Public|Any'&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;Profile&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Windows classifies networks as &lt;strong&gt;Private&lt;/strong&gt; (e.g. home or office) or &lt;strong&gt;Public&lt;/strong&gt; (e.g. a café). These rules &lt;strong&gt;accept inbound connections even on public Wi-Fi&lt;/strong&gt;. Windows' own rules will also show up in large numbers, so focus on &lt;strong&gt;apps you installed yourself&lt;/strong&gt;. Anything you don't use, or can't explain, is a candidate for review.&lt;/p&gt;

&lt;h3&gt;
  
  
  File share permissions
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-SmbShare&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-SmbShareAccess&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="bp"&gt;$_&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;Name&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;An &lt;code&gt;AccountName&lt;/code&gt; of &lt;code&gt;Everyone&lt;/code&gt; with &lt;code&gt;AccessRight&lt;/code&gt; of &lt;code&gt;Full&lt;/code&gt; means the share is wide open at the entrance.&lt;/p&gt;

&lt;h3&gt;
  
  
  Tamper Protection and the Guest account
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Get-MpComputerStatus&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;IsTamperProtected&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;Get-LocalUser&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;Guest&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="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If &lt;code&gt;IsTamperProtected&lt;/code&gt; is &lt;code&gt;False&lt;/code&gt;, you can turn it on under &lt;strong&gt;Windows Security → Virus &amp;amp; threat protection → Manage settings → Tamper Protection&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Backup
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;In your NAS (or backup tool) admin screen, look at &lt;strong&gt;the date of the latest snapshot&lt;/strong&gt;, not just whether a schedule exists&lt;/li&gt;
&lt;li&gt;Check that the backup drive &lt;strong&gt;isn't always connected and writable&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Router
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;In the admin screen, look at UPnP, WPS, remote (internet-side) administration, and port forwarding&lt;/li&gt;
&lt;li&gt;Check that firmware updates are automatic&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;p&gt;In this post we looked at the "devices" and "just in case" parts of what you need to protect, split into three layers — development environment, office infrastructure, and devices on Wi-Fi — and shared what we actually reviewed. Even with a setup built around an ordinary broadband router, the mix of factory defaults and convenience permissions left things to fix. And when we re-ran the same checks after our changes, we found two settings we had only thought we had. Here is what to check:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What to check&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Development&lt;/td&gt;
&lt;td&gt;What is running that can be reached from outside the PC / any share open to "Everyone" / whether antivirus can be turned off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Devices on Wi-Fi&lt;/td&gt;
&lt;td&gt;What you allow on public networks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Office infrastructure (router)&lt;/td&gt;
&lt;td&gt;Devices can't open holes on their own / updates haven't stopped / the admin screen isn't visible from outside&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Office infrastructure (backup)&lt;/td&gt;
&lt;td&gt;Can you roll back / can those versions be deleted from the PC / &lt;strong&gt;the latest date&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A setting is only a belief until you confirm it. &lt;strong&gt;After you change something, run the same check again.&lt;/strong&gt; That was the single most important lesson from this review.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This post is part of a series on security steps an individual or a very small business can take. It was first published in Japanese on &lt;a href="https://zenn.dev/exapolicy/articles/faaf498201d98e" rel="noopener noreferrer"&gt;Zenn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Exapolicy LLC builds Covenant, an AI governance app for individuals that checks what you are about to send to an AI service against rules you define, on your own machine, before it is sent. Covenant is not a ransomware or DDoS defense. This post is a record of a review of our own environment; following these steps does not guarantee you won't be affected.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>networking</category>
      <category>security</category>
      <category>ransomware</category>
    </item>
    <item>
      <title>List what you need to protect before you choose your defenses</title>
      <dc:creator>早川徳一</dc:creator>
      <pubDate>Mon, 12 Oct 2026 16:32:58 +0000</pubDate>
      <link>https://dev.to/exapolicy/list-what-you-need-to-protect-before-you-choose-your-defenses-1c5i</link>
      <guid>https://dev.to/exapolicy/list-what-you-need-to-protect-before-you-choose-your-defenses-1c5i</guid>
      <description>&lt;h2&gt;
  
  
  Where this starts
&lt;/h2&gt;

&lt;p&gt;Companies keep reporting leaks of their customers' personal data. In Japan, where we are based, the Digital Minister said at a press conference on October 6, 2026 that cyberattacks are not only a problem for companies and organizations, and asked individuals to take their own basic steps (&lt;a href="https://www.digital.go.jp/speech/minister-261006-01" rel="noopener noreferrer"&gt;Digital Agency, press conference summary, in Japanese&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Of course, once you have handed your information to a company, nothing you do afterwards gets it back. In &lt;a href="https://zenn.dev/exapolicy/articles/774a1241ec1688" rel="noopener noreferrer"&gt;an earlier post (in Japanese)&lt;/a&gt; we argued that this is exactly why you need a policy for the information you are &lt;em&gt;about&lt;/em&gt; to share: split it into "never share", "check before sharing" and "fine to share".&lt;/p&gt;

&lt;p&gt;But that policy is not enough on its own. If you don't also look after &lt;strong&gt;the environment you keep your information in&lt;/strong&gt; — which accounts, which devices, which backups — the information you decided never to share can &lt;strong&gt;still leak without you meaning it to&lt;/strong&gt;. If your PC is taken over, for example, the information you would never have shared walks out with it.&lt;/p&gt;

&lt;p&gt;This post is about the step before you secure that environment: &lt;strong&gt;listing what you need to protect&lt;/strong&gt;. It is the method we use to check our own company's information handling, rewritten so that individuals can use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Why start with a list
&lt;/h2&gt;

&lt;p&gt;When we reviewed our own environment (the next post covers that), none of the gaps we found had been created at once. They had built up, one permission at a time, for convenience.&lt;/p&gt;

&lt;p&gt;We noticed something else, too. The OS, the router and the apps &lt;strong&gt;all worked fine with their out-of-the-box settings&lt;/strong&gt;. Because they worked, we didn't notice what was missing.&lt;/p&gt;

&lt;p&gt;In &lt;a href="https://zenn.dev/exapolicy/articles/395aa0aede6c83" rel="noopener noreferrer"&gt;another post (in Japanese)&lt;/a&gt; we wrote that apps should work the moment you install them, but deciding what to protect is up to the person using them. Security is the same. &lt;strong&gt;Working and being protected are two different things.&lt;/strong&gt; Products get you as far as "it works". They don't decide what &lt;em&gt;you&lt;/em&gt; need to protect in &lt;em&gt;your&lt;/em&gt; setup.&lt;/p&gt;

&lt;p&gt;You can't see what's missing until you write it down. So this is the policy we follow, and the one this post recommends:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before choosing any defense, list what you need to protect — and keep that list alive.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The rest of this post is the rules that put this policy into practice: how to make the list (sections 2 to 5) and how to keep it alive (section 6).&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Sort what you protect onto five shelves
&lt;/h2&gt;

&lt;p&gt;For an individual, it helps to sort what you protect onto five shelves:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Shelf&lt;/th&gt;
&lt;th&gt;What goes on it (examples)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Accounts&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Email, bank and cards, app stores, social media, AI services, cloud storage, services you use for work&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Devices&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;PC, smartphone, router, NAS or external drives, smart home devices&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Data&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Your own personal data, &lt;strong&gt;other people's data you hold&lt;/strong&gt; (clients, partners, family), work files, passwords and keys&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Exits&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Sign-up forms, social media, AI services, file sharing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Just in case&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Backups, account recovery (recovery email, phone number, recovery codes), who to contact in an incident&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;You don't need to write everything down at once. &lt;strong&gt;Start with your email account.&lt;/strong&gt; Password resets for most other services arrive by email. Whoever controls your email can take over the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. For each shelf, write "fix it if this is true"
&lt;/h2&gt;

&lt;p&gt;Once you have the list, write down for each shelf &lt;strong&gt;the states that need fixing&lt;/strong&gt;. The trick is to phrase each row not as a goal ("do X") but as &lt;strong&gt;"if this is true, fix it"&lt;/strong&gt;. A goal is easy to tick off because you &lt;em&gt;think&lt;/em&gt; you've done it. A state you can actually check against where you are now.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Shelf&lt;/th&gt;
&lt;th&gt;Fix it if this is true (examples)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Accounts&lt;/td&gt;
&lt;td&gt;Multi-factor authentication (or a passkey) is off on any important account&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Accounts&lt;/td&gt;
&lt;td&gt;You reuse the same password across services&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Accounts&lt;/td&gt;
&lt;td&gt;Your recovery options live on a single device, or only in your head&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Accounts&lt;/td&gt;
&lt;td&gt;Accounts for services you no longer use are still open&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Devices&lt;/td&gt;
&lt;td&gt;OS or router updates have stopped&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Devices&lt;/td&gt;
&lt;td&gt;Some apps accept inbound connections even on public networks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data&lt;/td&gt;
&lt;td&gt;You keep other people's personal data you no longer need, with no end date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data&lt;/td&gt;
&lt;td&gt;Passwords or keys sit in plain text in notes, chats or screenshots&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Exits&lt;/td&gt;
&lt;td&gt;You have no step to check, before sharing, for information you decided never to share&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Exits&lt;/td&gt;
&lt;td&gt;You haven't drawn a line between what you may and may not give to AI services&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Just in case&lt;/td&gt;
&lt;td&gt;Your backup is always connected and writable (so it gets encrypted along with the PC)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Just in case&lt;/td&gt;
&lt;td&gt;Losing or breaking one PC would take your keys, passwords and important files with it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Just in case&lt;/td&gt;
&lt;td&gt;You would reset a password or change payment details on a phone call or email alone&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Just in case&lt;/td&gt;
&lt;td&gt;You &lt;strong&gt;haven't looked up&lt;/strong&gt; what to do first, or who to call, if something happens&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The three steps the Japanese Digital Minister asked people to take on October 6 map directly onto rows on the Accounts shelf:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;The minister's ask&lt;/th&gt;
&lt;th&gt;What the summary explains (paraphrased)&lt;/th&gt;
&lt;th&gt;Row in your list&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Stop reusing passwords&lt;/td&gt;
&lt;td&gt;If one service leaks, attackers can log in to other services with the same password. Use a different password for each service&lt;/td&gt;
&lt;td&gt;You reuse the same password across services&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Use multi-factor authentication&lt;/td&gt;
&lt;td&gt;Even if your ID and password leak, phone-based verification or one-time codes make unauthorized logins much less likely&lt;/td&gt;
&lt;td&gt;Multi-factor authentication (or a passkey) is off on any important account&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Watch out for suspicious email and SMS&lt;/td&gt;
&lt;td&gt;Phishing that impersonates real companies and government agencies is increasing. Don't open links casually; go through the official website or app&lt;/td&gt;
&lt;td&gt;You log in or enter details straight from links in email or SMS&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;None of the three is special. Written as rows in your list, each becomes something you can check yourself against.&lt;/p&gt;

&lt;p&gt;For reference, this is what we actually do on our own Accounts shelf:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Two-step verification is on for almost all of our accounts&lt;/li&gt;
&lt;li&gt;Passwords are kept in a password manager (no reuse)&lt;/li&gt;
&lt;li&gt;We use passkeys where services support them&lt;/li&gt;
&lt;li&gt;We don't click links in emails right away&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this is special either. But put next to the rows in the list, "almost all" turns into a clear next step: find out which ones are left.&lt;/p&gt;

&lt;p&gt;For the Data and Exits shelves, the three categories from the earlier post work as they are:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Category&lt;/th&gt;
&lt;th&gt;Examples&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Never share&lt;/td&gt;
&lt;td&gt;National ID numbers, credit card numbers, passwords, images of ID documents (except to services that require them)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Check before sharing&lt;/td&gt;
&lt;td&gt;Phone number, email address, home address, date of birth, employer, names and contact details of clients&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fine to share&lt;/td&gt;
&lt;td&gt;What is already on your public profile&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  4. Record one of three states
&lt;/h2&gt;

&lt;p&gt;We record the current state of each row as one of three:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;State&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;strong&gt;Confirmed&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;You checked that it's done, and have a record (a settings screen, a note)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Unchecked&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;There is no record that anyone has checked&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Undecided&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;You haven't decided what to do yet&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The important part: &lt;strong&gt;don't read "unchecked" as either "done" or "not done".&lt;/strong&gt; It only means nobody has checked. If you fill those gaps with "probably fine", the settings you only &lt;em&gt;think&lt;/em&gt; you have go straight into your list (it happened to us; the next post covers it).&lt;/p&gt;

&lt;p&gt;When we first built this list for our own company, there were more "unchecked" rows than we expected. Not because things weren't done, but because &lt;strong&gt;we had never checked&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Another perspective
&lt;/h2&gt;

&lt;p&gt;If you don't know what belongs on your list, &lt;strong&gt;look at it from another perspective: analyses of other people's incidents&lt;/strong&gt;. We took seven perspectives from a report that analyzed corporate data-leak cases:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;How much data you keep, and when you delete it&lt;/li&gt;
&lt;li&gt;Authentication and accounts&lt;/li&gt;
&lt;li&gt;What you expose to the internet, and how you keep it updated&lt;/li&gt;
&lt;li&gt;The outside services you rely on&lt;/li&gt;
&lt;li&gt;How you use AI (the permissions you give it, the outside documents it reads, whether a person checks its output)&lt;/li&gt;
&lt;li&gt;Backups, and your first moves in an incident&lt;/li&gt;
&lt;li&gt;Scams aimed at people (phone calls, emails, changed payment details)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That report, however, had been put together by an AI, and its case numbers didn't all agree. So &lt;strong&gt;we used the perspectives and left the numbers alone&lt;/strong&gt;. What you borrow is &lt;em&gt;what to look at&lt;/em&gt;, not &lt;em&gt;how often it happens&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Rules for keeping the list alive
&lt;/h2&gt;

&lt;p&gt;The second half of the policy is "keep that list alive". A list starts going stale the day you write it. Decide when you'll look at it again:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;When&lt;/th&gt;
&lt;th&gt;What to do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Once a month (pick a day)&lt;/td&gt;
&lt;td&gt;Go through the list from the top and update the states&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;When you start using a new service or device&lt;/td&gt;
&lt;td&gt;Add a row&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;When you change something&lt;/td&gt;
&lt;td&gt;Check it afterwards, and mark it "confirmed"&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Add a row whenever you start using something new.&lt;/strong&gt; Forget that, and permissions start piling up again outside the list.&lt;/p&gt;

&lt;p&gt;One more rule: &lt;strong&gt;look up how to respond before anything happens.&lt;/strong&gt; Incidents tend to arrive when you're busy. If you start researching then, you'll be slow — or make things worse with a well-meant move. Decide in advance what to do first and who to contact, and put it on one page (a later post in this series covers how).&lt;/p&gt;

&lt;h2&gt;
  
  
  7. The checklist (one A4 page)
&lt;/h2&gt;

&lt;p&gt;We put all of this on a single printable page: the five shelves, the "fix it if this is true" rows, a column for the state (confirmed / unchecked / undecided), and space for notes and the next review date. Print it, fill it in, and add or remove rows to fit your own setup.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F169atmgs1vvcagbowq3v.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F169atmgs1vvcagbowq3v.png" alt="What to protect — inventory checklist" width="800" height="1131"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;p&gt;This post covered how to list what you need to protect before you work on securing your environment. The policy is: &lt;strong&gt;before choosing any defense, list what you need to protect — and keep that list alive.&lt;/strong&gt; News of data leaks arrives almost daily, and we think an individual's setup could be targeted at any time. If you haven't done it yet, this may be a good moment to take stock of yours. In short:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Before choosing defenses, sort what you protect onto five shelves (accounts, devices, data, exits, just in case). Start with email&lt;/li&gt;
&lt;li&gt;For each shelf, write "fix it if this is true"&lt;/li&gt;
&lt;li&gt;Record the state as confirmed / unchecked / undecided — and don't read "unchecked" as "done"&lt;/li&gt;
&lt;li&gt;Take another perspective from other people's incidents; check numbers before you use them&lt;/li&gt;
&lt;li&gt;Pick a review day, and add a row whenever you start using something new&lt;/li&gt;
&lt;li&gt;Look up how to respond before anything happens&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If your policy decides how you share your information, this list is the map you apply that policy to.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This is the first post in a series on security steps an individual or a very small business can take. It was first published in Japanese on &lt;a href="https://zenn.dev/exapolicy/articles/31a680611207ad" rel="noopener noreferrer"&gt;Zenn&lt;/a&gt;. The next post is a record of how we reviewed the "devices" and "just in case" shelves in our own environment.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Exapolicy LLC builds Covenant, an AI governance app for individuals that checks what you are about to send to an AI service against rules you define, on your own machine, before it is sent. This post adapts the way we check our own company's setup for individuals; using this list does not guarantee you won't be affected.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>infosec</category>
      <category>privacy</category>
      <category>security</category>
    </item>
  </channel>
</rss>
