<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[MSCi]]></title><description><![CDATA[MSCi]]></description><link>https://msci1.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 16:13:29 GMT</lastBuildDate><atom:link href="https://msci1.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How Do You Build an AI Risk Register for ISO 42001?]]></title><description><![CDATA[How to build an AI risk register for ISO 42001: columns to include, how it differs from an IT risk register, and how often to review it.]]></description><link>https://msci1.hashnode.dev/how-do-you-build-an-ai-risk-register-for-iso-42001</link><guid isPermaLink="true">https://msci1.hashnode.dev/how-do-you-build-an-ai-risk-register-for-iso-42001</guid><category><![CDATA[AI]]></category><category><![CDATA[Security]]></category><category><![CDATA[compliance ]]></category><category><![CDATA[iso42001]]></category><category><![CDATA[Governance]]></category><dc:creator><![CDATA[MSCi]]></dc:creator><pubDate>Fri, 20 Nov 2026 12:43:54 GMT</pubDate><content:encoded><![CDATA[<p>An AI risk register records, for each AI system, what could go wrong, who is affected, how likely and severe it is, which controls apply and who owns the risk. ISO/IEC 42001:2023 expects documented AI risk assessment and treatment, so build the register from your AI inventory and review it on a fixed rhythm.</p>
<h2>What is an AI risk register?</h2>
<p>It is a living table of risks tied to specific AI systems. The standard is described on the <a href="https://www.iso.org/standard/81230.html">ISO site</a>. If you are starting out, an <a href="https://mscincorporation.com/en-US/aims-iso-42001-consultancy/">ISO 42001 consulting</a> engagement usually begins with the inventory and then the register.</p>
<h2>Which columns should it have?</h2>
<table>
<thead>
<tr>
<th>Column</th>
<th>What to record</th>
</tr>
</thead>
<tbody><tr>
<td>System</td>
<td>Name, version, vendor or in-house</td>
</tr>
<tr>
<td>Purpose</td>
<td>The decision or task it supports</td>
</tr>
<tr>
<td>Data</td>
<td>Inputs, training data sources, personal data</td>
</tr>
<tr>
<td>Affected people</td>
<td>Customers, staff, applicants, the public</td>
</tr>
<tr>
<td>Risk</td>
<td>What could go wrong (biased output, drift, misuse)</td>
</tr>
<tr>
<td>Likelihood / impact</td>
<td>Your scoring scale, applied consistently</td>
</tr>
<tr>
<td>Controls</td>
<td>Human oversight, testing, monitoring, access limits</td>
</tr>
<tr>
<td>Owner</td>
<td>A named person, not a team</td>
</tr>
<tr>
<td>Review date</td>
<td>When it was last checked</td>
</tr>
</tbody></table>
<h2>How is it different from an IT risk register?</h2>
<p>An IT register focuses on confidentiality, integrity and availability. An AI register adds impact on people, data quality, model behaviour over time, human oversight and reliance on third-party models. If you already run an ISMS, an <a href="https://mscincorporation.com/en-US/iso-27001-consultancy-services/">ISO 27001 consulting</a> partner can reuse your risk method instead of creating a new one.</p>
<h2>What about privacy and cybersecurity frameworks?</h2>
<p>Personal data in training or inputs links the register to privacy duties, where a <a href="https://mscincorporation.com/en-US/data-privacy-compliance/">data privacy consultant</a> can help. Teams aligned with the <a href="https://www.nist.gov/cyberframework">NIST Cybersecurity Framework</a> can ask a <a href="https://mscincorporation.com/en-US/nist-consultancy/">NIST consultant</a> to map overlaps.</p>
<h2>How often should we review it?</h2>
<p>Review at planned intervals and whenever a system, vendor or use case changes. Record each review.</p>
<h2>FAQ</h2>
<h3>Is an AI risk register legally required?</h3>
<p>ISO 42001 is voluntary. Laws and customer contracts may add their own requirements.</p>
<h3>Who issues an ISO 42001 certificate?</h3>
<p>An independent accredited certification body. MSCi prepares organisations; it does not certify them.</p>
<h3>Do we list every AI feature in vendor tools?</h3>
<p>List any that influence decisions about people or processes, and note the vendor.</p>
<h3>What is the biggest mistake?</h3>
<p>Scoring risks once and never updating them.</p>
]]></content:encoded></item><item><title><![CDATA[What Evidence Does an ISO 27001 Audit Ask For?]]></title><description><![CDATA[What evidence an ISO 27001 audit asks engineering teams for: access reviews, change records, logging, incident handling and vendor checks.]]></description><link>https://msci1.hashnode.dev/what-evidence-does-an-iso-27001-audit-ask-for</link><guid isPermaLink="true">https://msci1.hashnode.dev/what-evidence-does-an-iso-27001-audit-ask-for</guid><category><![CDATA[Security]]></category><category><![CDATA[compliance ]]></category><category><![CDATA[iso27001]]></category><category><![CDATA[Devops]]></category><category><![CDATA[SaaS]]></category><dc:creator><![CDATA[MSCi]]></dc:creator><pubDate>Thu, 19 Nov 2026 09:22:12 GMT</pubDate><content:encoded><![CDATA[<p>An ISO 27001 audit asks engineering teams for proof that controls actually run: access reviews, change approvals, logs and monitoring, incident records, backup tests, vulnerability handling and vendor checks. Auditors sample real records, so keep dated, owner-tagged evidence from day one instead of rebuilding it before the audit.</p>
<h2>What does an auditor mean by "evidence"?</h2>
<p>Evidence is a record showing a control ran as written, with a date and an owner. A policy says what you intend. A ticket, log export or signed review shows what you did. A reliable <a href="https://mscincorporation.com/en-US/iso-27001-consultancy-services/">ISO 27001 consulting</a> engagement starts by mapping each control to the record that proves it.</p>
<h2>Which records should engineers keep?</h2>
<table>
<thead>
<tr>
<th>Control area</th>
<th>Typical evidence</th>
<th>Usual owner</th>
</tr>
</thead>
<tbody><tr>
<td>Access control</td>
<td>Quarterly access review sign-offs, joiner/leaver tickets</td>
<td>Engineering manager, IT</td>
</tr>
<tr>
<td>Change management</td>
<td>Pull requests with approvals, deployment records</td>
<td>Engineering</td>
</tr>
<tr>
<td>Logging and monitoring</td>
<td>Alert rules, sample log exports, review notes</td>
<td>Platform/SRE</td>
</tr>
<tr>
<td>Incident handling</td>
<td>Incident tickets, post-incident reviews</td>
<td>Security lead</td>
</tr>
<tr>
<td>Backups</td>
<td>Restore test records</td>
<td>Infrastructure</td>
</tr>
<tr>
<td>Vulnerability management</td>
<td>Scan results, fix tickets, penetration test reports</td>
<td>Security, engineering</td>
</tr>
<tr>
<td>Supplier security</td>
<td>Vendor assessments, contracts</td>
<td>Procurement, security</td>
</tr>
</tbody></table>
<h2>How much evidence is enough?</h2>
<p>Auditors sample, so you need consistent records across the period, not a record for every event. Keep an evidence calendar with a date and owner per item. Testing results from <a href="https://mscincorporation.com/en-US/vapt-consultancy/">VAPT services</a> are common evidence for vulnerability management.</p>
<h2>How many controls does the standard have?</h2>
<p>The 2022 edition of ISO/IEC 27001 has 93 controls in Annex A, grouped into four themes (<a href="https://www.iso.org/standard/27001">ISO</a>). You choose which apply through your risk assessment, and you record that choice.</p>
<h2>Can the same evidence serve other frameworks?</h2>
<p>Largely yes. Card-data environments may need <a href="https://mscincorporation.com/en-US/pci-dss-consultancy/">PCI DSS consulting</a>, customers may ask for a <a href="https://mscincorporation.com/en-US/soc-consultancy/">SOC consultant</a> route, and many US buyers reference the <a href="https://www.nist.gov/cyberframework">NIST Cybersecurity Framework</a>, where a <a href="https://mscincorporation.com/en-US/nist-consultancy/">NIST consultant</a> can map overlaps. Tag each evidence item to every framework it supports.</p>
<h2>FAQ</h2>
<h3>Do we need a compliance tool to collect evidence?</h3>
<p>No. Tickets, repositories and shared folders work if dates and owners are clear.</p>
<h3>Who issues the ISO 27001 certificate?</h3>
<p>An independent accredited certification body. A consultancy prepares you; it does not certify you.</p>
<h3>What is the most common evidence gap?</h3>
<p>Access reviews that were done but never recorded.</p>
<h3>How early should evidence collection start?</h3>
<p>As soon as controls go live, so the audit sees a consistent history.</p>
]]></content:encoded></item><item><title><![CDATA[SOC 2 or ISO 27001 First? A Decision Guide for SaaS Teams]]></title><description><![CDATA[A practical comparison of SOC 2 readiness and ISO 27001 certification for SaaS teams: scope, evidence, timelines and which buyers ask for what.]]></description><link>https://msci1.hashnode.dev/soc-2-or-iso-27001-first-a-decision-guide-for-saas-teams</link><guid isPermaLink="true">https://msci1.hashnode.dev/soc-2-or-iso-27001-first-a-decision-guide-for-saas-teams</guid><category><![CDATA[Security]]></category><category><![CDATA[compliance ]]></category><category><![CDATA[SaaS]]></category><category><![CDATA[ISO]]></category><category><![CDATA[ISO 27001]]></category><category><![CDATA[SOC2]]></category><dc:creator><![CDATA[MSCi]]></dc:creator><pubDate>Wed, 18 Nov 2026 11:08:07 GMT</pubDate><content:encoded><![CDATA[<p>Choose by who is asking. If a US buyer has named SOC 2, do SOC 2 first. If you sell across regions or want one framework to organise your whole programme, start with ISO 27001. SOC 2 is an attestation report from a CPA firm. ISO 27001 is a certification from an accredited body.</p>
<h2>Which one are your buyers actually asking for?</h2>
<p>Check your last five security questionnaires. US enterprise buyers often ask for a SOC 2 report. International buyers more often ask for ISO 27001. Let the pipeline decide. If you need a readiness partner for the US route, see MSCi's <a href="https://mscincorporation.com/en-US/soc-consultancy/">SOC consultant</a> page.</p>
<h2>What is the difference between SOC 2 and ISO 27001?</h2>
<table>
<thead>
<tr>
<th></th>
<th>SOC 2</th>
<th>ISO 27001</th>
</tr>
</thead>
<tbody><tr>
<td>What it is</td>
<td>Attestation report</td>
<td>Certification</td>
</tr>
<tr>
<td>Who issues it</td>
<td>A licensed CPA firm</td>
<td>An accredited certification body</td>
</tr>
<tr>
<td>What it examines</td>
<td>Controls against the Trust Services Criteria</td>
<td>An ISMS against the standard</td>
</tr>
<tr>
<td>Evidence</td>
<td>Controls operating over a period (Type 2)</td>
<td>Management system plus audit cycle</td>
</tr>
</tbody></table>
<p>SOC 2 is defined by the <a href="https://www.aicpa-cima.com/resources/landing/system-and-organization-controls-soc-suite-of-services">AICPA</a>. ISO 27001 is published by <a href="https://www.iso.org/standard/27001">ISO</a>. SOC 2 is not a certificate, and MSCi's role is readiness and preparation, not issuing the report.</p>
<h2>Which should a SaaS startup do first?</h2>
<p>If your next large deal is US-based and the buyer named SOC 2, start there. If you sell across regions, an <a href="https://mscincorporation.com/en-US/iso-27001-consultancy-services/">ISO 27001 consulting</a> path gives you a management system you can reuse for SOC 2 later.</p>
<h2>Where do HIPAA and privacy fit?</h2>
<p>If you touch health data, plan for <a href="https://mscincorporation.com/en-US/hipaa-consultancy/">HIPAA consulting</a> early, since the <a href="https://www.hhs.gov/hipaa/index.html">HIPAA safeguards</a> overlap with both frameworks. If privacy is a growing buyer ask, an <a href="https://mscincorporation.com/en-US/iso-27701-pims-consultancy-services/">ISO 27701 consultant</a> can show how privacy controls attach to your security work.</p>
<h2>FAQ</h2>
<h3>Can one set of evidence serve both?</h3>
<p>Largely yes. Access reviews, change management, incident logs and vendor assessments are shared. Keep one evidence calendar and tag each item to both frameworks.</p>
<h3>Is a SOC 2 report the same as being certified?</h3>
<p>No. SOC 2 is an attestation report, not a certificate.</p>
<h3>Do we need to buy a compliance tool?</h3>
<p>Not necessarily. Tools help with evidence collection, but neither framework requires a particular product.</p>
<h3>How do we choose a consultant?</h3>
<p>Ask who owns the evidence once the consultant leaves, and how they separate readiness work from the independent assessment.</p>
]]></content:encoded></item></channel></rss>