<?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: AnkitS</title>
    <description>The latest articles on DEV Community by AnkitS (@itsupport247).</description>
    <link>https://dev.to/itsupport247</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%2F4196590%2F95cfff41-c941-4682-ad84-d0e133973740.png</url>
      <title>DEV Community: AnkitS</title>
      <link>https://dev.to/itsupport247</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/itsupport247"/>
    <language>en</language>
    <item>
      <title>ISO 27001 Annex A Controls: How to Choose and Record Them</title>
      <dc:creator>AnkitS</dc:creator>
      <pubDate>Tue, 20 Oct 2026 16:58:26 +0000</pubDate>
      <link>https://dev.to/itsupport247/iso-27001-annex-a-controls-how-to-choose-and-record-them-3edb</link>
      <guid>https://dev.to/itsupport247/iso-27001-annex-a-controls-how-to-choose-and-record-them-3edb</guid>
      <description>&lt;p&gt;Annex A of ISO 27001 lists 93 controls, which makes many people assume they must implement all of them. They do not.&lt;/p&gt;

&lt;h2&gt;
  
  
  A technical primer
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Annex A groups controls into organisational, people, physical and technological themes.&lt;/li&gt;
&lt;li&gt;Your risk assessment decides which controls you need.&lt;/li&gt;
&lt;li&gt;Annex A is then used to check you have not missed any.&lt;/li&gt;
&lt;li&gt;The Statement of Applicability records what you chose, its status and the reason for any exclusion.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Auditors will ask for evidence that each selected control actually operates.&lt;/p&gt;

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

&lt;p&gt;If your risk assessment flags lost laptops, you might select controls for device encryption, remote wipe and an asset inventory. Each one is recorded, given an owner and backed by evidence.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical next step
&lt;/h2&gt;

&lt;p&gt;If a control does not apply, such as secure development for a business that writes no software, record that and the reason. A clear reason is accepted by auditors. A blank is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to go next
&lt;/h2&gt;

&lt;p&gt;If you want more detail, read &lt;a href="https://itsupport247.technology/blog/iso-27001-controls-annex-a/" rel="noopener noreferrer"&gt;Annex A explained with examples&lt;/a&gt; on the IT Support 247 blog. If you would like help applying it to your own organisation, see &lt;a href="https://itsupport247.technology/services/iso-27001/" rel="noopener noreferrer"&gt;ISO 27001 guidance for Australian businesses&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;IT Support 247 is a Melbourne IT support and compliance provider working with organisations across Australia.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
    </item>
  </channel>
</rss>
