

Content Contributor, E-N Computers
More than a decade of experience in technical support including end user support, mobile device management, application deployment, and documentation.
Most RIA risk assessment templates you’ll find online are blank. We’re sharing one that’s filled in, so you can see how to score each risk, what evidence to keep and which rows need IT’s help before you start on your own.
Below is a completed cybersecurity risk assessment for a made-up ten-person registered investment adviser (RIA). It also scores AI tool use, which the SEC says examiners will check in 2026. We provide a blank template that’s free to download, with no email required to get it. [Jump link to download section]
A risk assessment lists the risks to client information, scores each one and records what the firm does about it. For a CCO, it’s how you check that your security policy matches your systems. If the policy promises multi-factor authentication and encryption, an examiner can ask you to show where. That proof often sits in systems and vendor contracts you don’t control.
QUICK ANSWER:
Question goes here
The answer to the question goes here. This is sample text. This is sample text. This is sample text.
Table of Contents
- Risks are listed, rated, and given an owner
- Sample firm: ten people, no server, and a policy that promises more than the IT delivers
- Eight systems and vendors touch client data, and the firm administers two of them
- Four of the eight vendor contracts have no 72-hour breach notice term
- Wire fraud scores highest at 9, and seven more risks score 6
- You need to score AI tool risk, too
- Your compliance officer needs IT input
- Your high risk items need to be in your WISP
In a hurry? Click here to download the RIA cybersecurity risk assessment template.
Risks are listed, rated, and given an owner
A completed cybersecurity risk assessment for an RIA is a table that lists your risks, scores each one for likelihood and impact, lists the control you have in place, and says who owns it.
Regulation S-P (Reg S-P) is the Securities and Exchange Commission (SEC) rule on protecting client information. It doesn’t directly require a risk assessment. Instead, it requires written policies reasonably designed to protect against anticipated threats. Still, a risk assessment is a practical way to show that your policies fit your systems and threats. It also feeds your annual compliance review.
Larger firms had to comply with the amended Reg S-P rule by December 3, 2025, and smaller ones by June 3, 2026. The SEC’s fiscal 2026 exam priorities say examiners will check that firms have written these policies, put them in place and kept them up to date.
Download the blank RIA cybersecurity risk assessment template

Hiring good IT personnel isn’t easy. We’ve found three roles work well with a co-managed IT service plan. And we’ve created sample job descriptions to help you find the right people for the job.
Don’t have time for the job descriptions right now? Enter your email address (totally optional!) and we’ll send you a link so you can download them later or share them with your team.
Sample firm: ten people, no server, and a policy that promises more than the IT delivers
We made up this firm to show what a risk assessment might look like.
- $300M AUM
- 10 employees
- One office
- No server
- Email managed by broker-dealer or parent firm
- Company workstations and personal phones
The firm’s written security policy came from its upstream partner. It promises multi-factor authentication (MFA) and encryption. As a smaller firm, it had to comply with the amended rule by June 3, 2026.
A ten-person office with no server, computers that share files directly with each other and no control over its email or sign-in provider is typical for a small RIA, said Ian MacRae, president of E-N Computers.
Eight systems and vendors touch client data, and the firm administers two of them
A risk assessment starts with an inventory of where client information lives and who runs each system. In our sample, vendors host three systems. The custodian runs one, the upstream partner (e.g., broker-dealer or parent firm) runs email, the IT provider holds administrative access, and the firm manages two itself, the CRM and file storage. Each system has its own contract.
| System or vendor | Client data it holds | Who administers it |
| Custodian portal | Account numbers, balances, trades, client identity | Custodian; the firm manages user logins |
| Client correspondence, statements, wire instructions | Upstream partner | |
| CRM | Contact details, dates of birth, account notes | Firm |
| Financial planning software | Income, net worth, tax data | Vendor-hosted |
| Portfolio reporting software | Holdings, account numbers | Vendor-hosted |
| File storage | Onboarding forms, ID scans, signed agreements | Firm |
| Client portal | Statements, documents | Vendor-hosted |
| IT provider | Administrative access to firm systems and devices | IT provider |
Fictional firm. All values are invented.
Four of the eight vendor contracts have no 72-hour breach notice term
Under the amended rule, the firm’s written policies have to be set up so its vendors report a breach of any system they maintain within 72 hours of learning about it. A clause in each vendor contract is the usual way to do that. The firm has its own deadline, too. It has to notify affected clients as soon as practicable, and no later than 30 days after it learns that someone got into client information without permission, or likely did.
For our sample firm, the CRM, financial planning software, client portal and IT provider agreements include the 72-hour term. The custodian, email, portfolio reporting and file storage contracts either say nothing or have standard terms nobody has reviewed. That gap becomes risk R5 in the risk register below.
| Vendor | Breach-notice term in contract | 72-hour term? |
| Custodian portal | Set by the custodian; the firm has not reviewed it | No |
| Silent | No | |
| CRM | 72 hours | Yes |
| Financial planning software | 72 hours | Yes |
| Portfolio reporting software | Silent | No |
| File storage | Standard terms; not reviewed | No |
| Client portal | 72 hours | Yes |
| IT provider | 72 hours in the service agreement | Yes |
Fictional firm. No real vendor is named.
Wire fraud scores highest at 9, and seven more risks score 6
Each risk gets two scores from 1 to 3, one for likelihood and one for impact. Multiply them to get the risk score. A likelihood of 3 means the risk is likely, or has already happened at this firm or one like it. An impact of 3 means money moves, many clients are affected, or the firm has to notify clients. You can set your own scale for low, medium, and high risk. In our example:
- High: 7+
- Medium: 3–6
- Low: 0–2
| ID | Risk | L × I | Score | Band | Current control |
| R1 | Wire fraud through a compromised email account | 3 × 3 | 9 | High | Multi-factor sign-in on email, not on every platform; no written callback rule |
| R2 | Stolen custodian portal credentials | 2 × 3 | 6 | Medium | Individual logins; multi-factor sign-in set by the custodian; no access review |
| R3 | Client data on unmanaged personal phones | 3 × 2 | 6 | Medium | Office devices encrypted; personal phones unmanaged; no personal-device policy |
| R4 | Departing adviser takes client files | 2 × 2 | 4 | Medium | Verbal offboarding |
| R5 | Vendor breach with no contractual notice | 2 × 3 | 6 | Medium | Four of eight vendor contracts lack a 72-hour notice term |
| R6 | Lost or stolen laptop | 2 × 2 | 4 | Medium | Laptops encrypted |
| R7 | Ransomware with an untested backup | 2 × 3 | 6 | Medium | Nightly backup of file storage; restore never tested; patching is infrequent |
| R8 | Staff paste client data into AI tools | 3 × 2 | 6 | Medium | No rule; staff use free tools |
Fictional firm. L × I is likelihood times impact.
One row scores High. Wire fraud (R1) tops the list because it’s both likely and severe: multi-factor sign-in covers email but not every platform, and the firm has no written rule to call a client back before moving money.
Everything else scores as Medium. A departing adviser taking client files (R4) is fixed with a written offboarding checklist. A stolen laptop (R6) is decided to be an acceptable risk because the laptops are encrypted. It checks the encryption report each quarter and will review the decision after one year. Each row is accompanied by a decision to fix or accept, and a date for follow-up.
Remember to score the risk of AI tools
Staff pasting client data into AI tools (R8) scores 6, which is Medium, with a likelihood of 3 and impact of 2. In the sample, staff use free AI tools, and the firm has no rule about what client information can go into them.
The fix has three parts: a written AI use policy with an approved tool list, a rule that client information goes only into approved tools, and training so staff know both. The firm decides which tools are approved. Whoever manages the firm’s computers can then enforce the list.
The SEC’s fiscal 2026 exam priorities say examiners will check whether firms have policies to supervise how they use AI. A policy, an approved list and a training record are the evidence worth having on file if a reviewer asks.
Your compliance officer needs IT input
The owner column separates what the CCO decides from what needs proof from IT. The firm owns six rows, and its IT provider (ENC in this sample) owns two. The legal duty stays with the firm in every row. The owner runs the work and gets the evidence on file. In four rows, that evidence lives in IT systems, and the owner can’t produce it alone.
| ID | Owner | Evidence to keep on file | Decision |
| R1 | Firm | MFA coverage report from the email provider; log of callback verifications | Fix by Dec 15, 2026 |
| R2 | Firm | Dated user access list with reviewer sign-off | Fix by Jan 15, 2027 |
| R3 | Firm | Written personal-device policy; device inventory | Fix by Jan 31, 2027 |
| R4 | Firm | Offboarding checklist with access-removal dates | Fix by Dec 31, 2026 |
| R5 | Firm | Executed contracts showing the term; due-diligence file per vendor | Fix by Feb 28, 2027 |
| R6 | MSP | Encryption status report per device | Accept. Revisit Oct 29, 2027 |
| R7 | MSP | Backup restore test record; patch report | Fix by Jan 31, 2027 |
| R8 | Firm | Written AI use policy; approved tool list; training record | Fix by Dec 15, 2026 |
Fictional firm. MSP in the Owner column stands for the firm’s managed IT service provider. R1, R3, R6 and R7 need evidence from IT systems.
Those four are the MFA coverage report (R1), the device inventory (R3), the encryption report (R6), and the restore test and patch report (R7). Those last two show that backups work and updates get installed. The CCO needs IT to produce those.
A good risk assessment pulls in technical data, Ian said, including known security weaknesses, how current software updates are, and the state of backups and disaster recovery. If a firm fixes security weaknesses on only one maintenance day a year, he said, that belongs in the assessment. He added that the compliance team needs a knowledgeable IT person in the meeting. Without one, the result is unreliable because you won’t be able to accurately describe the technical implementation of the controls.
High risks items need to be in your WISP
The risk register feeds the written information security program (WISP), which describes what the firm does to protect client information.
Many firms’ plans promise encryption and MFA with no IT work behind them, Ian said. The document says one thing, and the systems do another. R1 is that problem in the sample: the policy promises multi-factor authentication, and only email has it.
The next piece in this series turns the register into a WISP section by section.
Let us help you fill in the IT blanks
Can you say what multi-factor sign-in covers, whether anyone has tested a backup restore, or what your vendor contracts say about breach notice? Those are the most common places where a compliance officer can use the help of IT professionals.
E-N Computers is a managed IT provider for financial firms, defense contractors, and other regulated businesses in Virginia and the Washington, D.C., area. We run risk assessments with our RIA clients. You make the decisions, while we set technical controls and produce evidence of implementation.
We also run tabletop exercises, a practice walk-through of a breach, for RIA clients as an optional part of our compliance package. A tabletop exercise lets you practice incident response and produces a record you can show to a regulator. Schedule your complimentary consultation today.
Not sure if you need managed IT services?
Take the IT Maturity Self-Assessment

In a few minutes, get actionable insights on your IT strategy, plus a free strategic consultation.

Industries
Locations
Waynesboro, VA
Corporate HQ
215 Fifth St.
Waynesboro, VA 22980
Sales: 540-217-6261
Service: 540-885-3129
Accounting: 540-217-6260
Fax: 703-935-2665
Washington D.C.
1126 11th ST. NW
Suite 603
Washington, DC 20001-4366
Sales: 202-888-2770
Service: 866-692-9082
VA DCJS # 11-6604
Locations
Harrisonburg, VA
45 Newman Ave.
Harrisonburg, VA 22801
Sales: 540-569-3465
Service: 866-692-9082
Richmond, VA
3026A W. Cary St.
Richmond, VA 23221
Sales: 804-729-8835
Service: 866-692-9082
