Financial Cybersecurity in North Texas: What to Document in 2026

A practical checklist for 10-to-50-person financial firms: the controls to enforce, the evidence to keep, and the steps to take when a mailbox or payment looks compromised.

By the Total 360 Technology team11 min read
Compliance director reviewing a financial cybersecurity control register in a binder at an office table in Turtle Creek

Picture a Dallas wealth manager opening a cyber insurance renewal questionnaire in late October and finding that the helpdesk cannot show MFA or endpoint monitoring enforced on every account. For a 10-to-50-person financial practice, financial cybersecurity means a short set of controls you can prove on demand: enforced MFA and conditional access, removed local admin rights, a verified step before any payment changes, backups you have restored, and containment that works at 2 a.m. Check each one against the rule that governs your firm and the questionnaire you will sign, and write down the evidence as you go.

This guide is for the managing partner or compliance director who has to sign those answers. It walks through the controls in the order most firms should check them, what evidence each one produces, and the steps people tend to skip.

Which rules govern your firm and what they ask you to write down

Many non-bank financial firms fall under the FTC Safeguards Rule, which implements the Gramm-Leach-Bliley Act. Depending on your registration and the work you do, SEC or FINRA expectations may also reach you. The frameworks financial firms are commonly measured against include GLBA Safeguards, SEC cybersecurity requirements, FINRA expectations, the FFIEC IT Examination Handbook, NYDFS and PCI DSS for card data. Compliance is expected to be continuous and documented, not a binder assembled the week before an exam.

Across these regimes the written artifacts tend to look the same:

  • A named qualified individual who owns the information security program.
  • A written risk assessment that ranks risks, assigns an owner to each and sets a remediation date.
  • Access controls, with MFA for anyone who reaches customer information.
  • Encryption of customer data in transit and at rest.
  • Logs of authorized user activity, because an examiner will ask what was accessed and when.
  • A written incident response plan.
  • A written report to the board or owners at least once a year.

Confirm the testing intervals and the exact required elements against the text of the rule that applies to your registration before you set your calendar. Summaries, including this one, are a starting point, not a substitute for the rule.

Which rule covers which part of the firm

Map each rule to the systems it reaches, starting with where client files live and the email that carries them. Where one system falls under two rules, document the stricter requirement. A gap at this stage is cheap to fix; a gap discovered by an examiner is not.

The written program a named owner can defend

A risk assessment that cannot show which risks outrank others, who owns each one and when it will be fixed is a list, not a program. Keep it short enough that someone will actually update it. For the broader compliance picture, see our page on Texas SB 2610 compliance, and for how a written program earns safe-harbor credit, read how Texas SB 2610 protects you.

Why a helpdesk ticket fails the renewal questionnaire and the audit

A ticket proves that someone did work. It does not prove that a control is enforced on every account, every day. An underwriter or examiner is asking a different question: is the rule in force now, across the whole firm, and can you show it? Ask any provider to show you the policy that blocks a sign-in, not the ticket that fixed one.

Most gaps on a renewal questionnaire are settings the firm already paid for and never enforced. Conditional access that exists but applies to only a few groups, a legacy sign-in method left switched on, an administrator account with no MFA because it was exempted during setup and nobody revisited it. These gaps are invisible in a ticket queue and obvious in a policy report.

Ask for the policy, not the ticket

When you evaluate a provider, ask them to produce, for your tenant:

  1. The conditional access policy list, with the users and groups each policy covers.
  2. A report showing MFA registration and enforcement across every account, administrators included.
  3. A sample sign-in log for one executive and one administrator.
  4. The list of accounts holding administrator rights, with the date that list was last reviewed.

Answer each yes with a setting, a report and a log

Build a simple control register: each safeguard, its owner, the evidence that proves it, and the date it was last reviewed. Regulators expect risks ranked with owners and deadlines. A firm that cannot produce this register will spend its audit time reconstructing it from memory and email. The cybersecurity audit guide covers what underwriters check in more detail, and our security-controlled operations page explains how these controls are run as one program.

How do you stop wire fraud that arrives as a believable email

How do you stop wire fraud that arrives as a believable email, Total 360 Technology

Most wire fraud at a financial practice starts with a believable email, not a technical break-in. A message appears to come from the managing partner, a client or a title company, with a new account number or an urgent request to move funds. The attacker has often been reading the mailbox for weeks. Among the attacks most commonly aimed at financial firms are business email compromise, phishing and credential theft, and the defense is the same for all of them: a verification step outside email for any new or changed payment instruction, enforced as a written rule that staff cannot skip under time pressure.

Make the verification step a written rule

  1. Any new payee, changed account number or changed routing detail is verified by a phone call to a number already on file, not one supplied in the message.
  2. The person who requested the change cannot be the only person who approves it.
  3. Any payment above a threshold you set requires a second approver who confirms by a channel outside email.
  4. The rule is written down, signed by every person who can release funds, and tested at least once a year.

Expect the request that arrives under a deadline

The request that succeeds is usually the one that sounds routine and arrives on a Friday afternoon or the day before a closing. Train staff that urgency is a reason to slow down, not speed up. When a mailbox looks compromised, check the forwarding rules and inbox rules first. Attackers often hide a forward to an outside address and leave the password alone, so a password reset alone will not close the exposure. For how phishing defense fits into email protection, see our page on enforced operational safeguards.

How do you enforce MFA and conditional access without breaking month-end

Conditional access should block legacy sign-in methods, require MFA for administrators and anyone reaching client data, and limit access to managed devices. The protection only helps if it stays on. A rollout that breaks month-end gets reversed, and the protection goes with it, so sequence the work.

Start with administrators and finance staff

Enforce MFA for administrator accounts first, then for anyone who approves or releases payments, then for everyone who reaches client data. Widen the rule once a full month-end cycle has run cleanly. Prefer number matching or app-based approval over SMS codes where the platform allows it. Watch for approval prompts nobody started: when prompts arrive constantly, people approve what they did not initiate. If the sign-in log shows prompts you cannot explain, investigate before you assume a glitch.

For staff who need the strongest protection, a hardware key is worth the effort. Our guide to FIDO2 security keys for small firms covers a rollout that avoids lockouts, and secure remote access solutions explains how to limit what each account can reach once it signs in.

Remove local admin rights on one machine first

Removing local administrator rights from laptops is worth doing, but do it in a planned way. Inventory the software that needs elevation to install or update. Approve those specific installers. Test the change on one machine, then roll it out firm-wide on a planned date with a named person to handle requests. The guidance in our Windows security controls checklist follows the same order. If you skip the inventory, the first update that fails will get the change reversed.

Why sync is not a backup and how do you prove recovery

Why sync is not a backup and how do you prove recovery, Total 360 Technology

Cloud sync, standard cloud backup and immutable disaster recovery are three different things. Sync copies whatever changed on one device to another location. If files encrypt on a laptop, the sync client often copies the encryption to the cloud, so you have ransomware in two places. Standard cloud backup may keep older versions, but if the production accounts can delete them, so can an attacker. Immutable recovery means versioned copies that the production accounts cannot delete or alter for a set period.

A backup you have never restored is a hypothesis. The test log is what an auditor or insurer will ask to see.

  1. Confirm that at least one set of backup copies is held where the production administrator accounts cannot delete or change it.
  2. Set a written restore-test schedule, quarterly is a sensible default for a firm this size.
  3. Restore a sample of files and at least one full system, not just a single document.
  4. Record the date, what was restored, how long it took, what failed and who signed off.
  5. Fix what failed and retest it before closing the entry.

North Texas adds its own pressure. Severe spring storms and unpredictable winter freezes across the ERCOT grid mean a restore plan has to work when your office is dark and your staff cannot get in. Our page on data backup and disaster recovery testing covers the testing rules in detail.

How do you verify 24x7 containment without an in-house SOC

Antivirus stops known malware. Managed detection and response watches behavior across endpoints and acts on what it sees. A firm without an in-house security operations center does not need one, but it does need to know who can isolate a compromised machine at 2 a.m., how that action is logged, and who the firm is called to confirm it. If nobody can isolate a machine at night, you do not have 24x7 protection, whatever the product sheet says.

Ask who isolates a machine at night

Put these questions to any provider in writing:

  • Who has the authority to isolate an endpoint outside business hours, and how fast do they act?
  • What triggers an isolation, and does the trigger create a log entry?
  • Who in your firm is called, by what channel, and what must they approve?
  • Can you see a sample report of an isolation from the last quarter, with timestamps?

Check the log, not the promise

Ask for the log. A provider that can produce an actual isolation record with times, the affected device and the follow-up is describing a process. A provider that describes its service in general terms is asking you to trust the description. Our explainer on what MDR does and the comparison of MSSP and SOC models can help you decide which questions matter most for a firm your size.

What do you do first if a mailbox or payment looks compromised

Start by stopping the spread. Then preserve the evidence before anyone changes it.

  1. If you find unfamiliar administrator accounts, unexplained forwarding rules or a payment change already sent, stop investigating inside the affected mailbox.
  2. Call an incident responder. Tell them what you saw and when.
  3. Preserve the sign-in logs, audit logs and mailbox rules before anyone resets a password or deletes a rule. Once they are gone, the evidence of what happened is gone with them.
  4. Contact your bank about any payment already sent, using a phone number you already have.
  5. Only then reset credentials, revoke sessions and remove forwarding rules, in the order your responder advises.
  6. Record every action with a time, because your insurer and possibly your regulator will ask for the timeline.

Debunking a false claim quickly depends on the same thing. When extortion demands arrive, maintainable logs let you show what was and was not accessed. Municipal authorities in Princeton recently investigated extortion claims from a ransomware group, and two independent technical reviews found no evidence of unauthorized internal network compromise. Logs that cover the right systems are what let a firm answer that question quickly.

What to ask a Dallas provider before you sign

Choosing a provider is a security decision as much as a price decision. Total 360 Technology provides security-controlled IT operations for Dallas-Fort Worth firms with 10 to 50 users. Our financial services practice is built around the controls in this guide: enforced MFA and conditional access, administrative privilege reduction, backup verification with periodic recovery testing, and 24x7 managed detection and response. Hardware is provided at cost plus 5%, and pricing is flat-rate, without surprise hourly ticket billing. Those are commitments you can check in writing before you sign, and we would expect any provider you consider to put its own commitments in writing too.

Use this list to compare any provider, including us:

  • Can they show the conditional access policy list and the MFA enforcement report for your tenant?
  • Who isolates an endpoint at 2 a.m., and can they show a sample log?
  • When did they last run a full restore test, and can they show the record?
  • Is pricing flat-rate, and does it include after-hours containment?
  • How is hardware priced, and is the markup disclosed?
  • Will they help you build the control register that your insurer and examiner will ask for?

If you want to see how these controls would apply to your firm, book a 30-minute security discussion through our consultation page. Bring your current renewal questionnaire and we will walk through which answers you can prove today and which need work. For the financial services practice itself, see managed IT for financial services. For Texas-specific context, read our guide to what owners should demand from a managed service provider.

Frequently asked questions

What documentation will a cyber insurance renewal questionnaire ask for regarding MFA enforcement and privileged access?

For each yes answer, show the enforced setting, a report proving the policy covers every account rather than most, and a sample sign-in log. Also list who holds administrator rights and the date that list was last reviewed. The full underwriter checklist is in our cybersecurity audit guide.

How often should a financial practice test its offsite backup recovery?

On a written schedule the firm sets and keeps, with a dated record of what was restored, how long it took and what failed. Quarterly is a sensible default for a practice of this size. The test log is the evidence an auditor or insurer asks to see; a backup that has never been restored is not yet a recovery plan.

Can you enforce multi-factor authentication without slowing down daily employee logins?

Yes, by choosing number matching or app approval over SMS where the platform allows it, starting with administrators and finance staff, and widening the rule once month-end runs cleanly. Watch for approval prompts nobody started, since constant prompts train people to approve without reading.

How do we remove local admin rights on employee laptops without breaking software?

Inventory the software that needs elevation to install or update, approve those specific installers, test the change on one machine, then roll it out firm-wide on a planned date with a named person to handle requests.

Is cybersecurity worth the cost for a 10-to-50-person financial practice?

Compare the cost of one misdirected wire, a failed renewal or a long audit reconstruction against the cost of controls the firm has to document anyway. The controls an insurer and an examiner ask for are the same ones that stop the losses, so the comparison should rest on documented evidence rather than tool prices.

Total 360 Technology provides security-controlled IT operations and cybersecurity for businesses in the Dallas-Fort Worth area with 10 to 50 users. We focus on enforced safeguards, proactive risk management, and 24x7 managed detection and response rather than traditional reactive IT support.

Serving Dallas, Fort Worth, Napa, Sonoma.