Protecting Your Insurance Agency Management System

Securing an insurance agency management system

Your agency management system, or AMS, is one of the most important tools in your business. It holds client information, policy details, documents, activity notes, and much of the history your staff relies on to serve customers.

Because the AMS is usually hosted by a software provider, it is easy to assume the provider handles all of its security. The provider operates the platform, but your agency still controls who can sign in, which devices they use, what integrations are connected, and where information goes after it leaves the system.

Those everyday decisions are where many preventable problems begin. They are also why AMS security belongs in the larger cybersecurity program of a New York insurance agency subject to NYDFS Part 500.

Why Your AMS Deserves Attention

An AMS brings a large amount of valuable information together in one place. That makes the agency more efficient, but it also means one compromised account can expose far more than a single document or email.

The most likely problem is not someone breaking into the AMS provider’s data center. It is someone signing in with a stolen password, using an account that should have been removed, accessing the system from an unsafe computer, or taking advantage of an integration that nobody reviews anymore.

Securing the AMS starts with understanding how your agency actually uses it. Know who has access, what information they can reach, which systems connect to it, and what happens to client information when it is downloaded or shared.

Start with the People Who Can Sign In

Every AMS user should have an individual account. Shared accounts make it difficult to know who performed an action and create problems when passwords need to be changed or an employee leaves.

Give each person only the access needed for the job. A producer, account manager, bookkeeper, and system administrator may need different permissions. Administrative access should be limited because those accounts can usually make the most significant changes.

Enable multi-factor authentication using the strongest practical option supported by the AMS. MFA adds another step at sign-in, which can stop a stolen password from becoming a successful intrusion.

Access should be reviewed periodically and whenever someone changes roles. When an employee or contractor leaves, remove AMS access promptly as part of the same offboarding process used for email, computers, carrier portals, and other business systems.

Protect the Devices and Email Accounts Around It

A secure AMS account can still be exposed through an unsafe computer. Devices used for agency work should receive security updates, use current endpoint protection, and be managed consistently. Employees should avoid accessing the AMS from shared or personal devices that the agency cannot properly secure.

Email security matters too. Phishing messages often imitate software vendors, carriers, or Microsoft sign-in pages. An employee who enters a password into a fake page may give an attacker what they need to reach several connected systems. MFA, employee training, and a clear way to report suspicious messages all reduce that risk.

Pay Attention When Information Leaves the AMS

Reports, spreadsheets, policy documents, and client records may be well protected inside the AMS but handled very differently after someone downloads them. An export saved to a desktop, personal device, or open shared folder is no longer protected by the AMS provider’s controls.

Store exported information only in approved locations with appropriate access restrictions. Use an approved secure method when sending sensitive documents, and remove files when there is no longer a business or legal reason to retain them. The goal is to avoid creating unnecessary copies of client information that become difficult to track and protect.

Vendor Risk Management for Your AMS and Connected Tools

An AMS may connect to carrier services, rating tools, document systems, accounting applications, email, or other vendors. These integrations save time, but each connection creates another path to agency information.

Vendor risk management, also called third-party risk management, means understanding which outside companies can reach your systems or information and how that access is protected. It does not need to begin with a complicated scoring system. Start by identifying the AMS provider and the connected vendors that could create the greatest disruption or expose the most sensitive information.

Maintain a simple record of active integrations, what each one does, what information it can access, and who is responsible for it. For higher-risk vendors, review the security information they make available and understand how they manage access, protect data, recover from outages, and notify customers about incidents. Remove connections that are no longer used.

Third-party risk management is not a one-time task. Revisit important vendors when contracts renew, services change, new integrations are added, or an incident raises concerns. Keep notes about what was reviewed and any follow-up work the agency decided to complete.

Learn how vendor oversight fits into our compliance management services.

Use the Alerts and Records Your AMS Provides

AMS platforms do not all provide the same reporting. Ask the provider which login records, account-change history, export reports, and security alerts are available. Also find out how long that information is retained.

Decide who will review useful alerts and what should happen when something looks unusual. Unexpected account changes, unfamiliar sign-ins, or unusually large exports deserve attention. Even a simple review process is better than collecting information that nobody ever checks.

Plan for an Outage or Suspicious Activity

Your AMS provider generally controls platform backups and recovery. Your agency should still understand what the provider promises, how incidents are communicated, and how long recovery may take. Decide how employees will handle urgent client needs and communicate with carriers if the AMS is temporarily unavailable.

Employees should also know whom to contact if they notice suspicious activity or believe an account has been compromised. A fast internal report gives the agency and its technology providers more time to protect accounts, preserve information, and determine what happened.

Some cybersecurity incidents must be reported to NYDFS as promptly as possible, but no later than 72 hours after the agency determines that a qualifying incident occurred. Whether an event is reportable can require legal and factual judgment, so escalation contacts should be established before an emergency.

How This Supports NYDFS Part 500

AMS security connects to several practical areas addressed by NYDFS Part 500, including risk assessments, asset records, access controls, MFA, employee training, vendor oversight, and incident notification. The exact requirements that apply depend on the agency’s regulatory status and circumstances.

This article is a security guide rather than a complete explanation of the regulation. For a broader overview, visit our NYDFS Part 500 requirements and compliance support page.

Making AMS Security Manageable

You do not need to redesign the entire agency at once. Start by confirming who can access the AMS, enabling MFA, removing old accounts, and identifying the devices and integrations connected to it. Those steps address some of the most common and preventable gaps.

Pickard Solutions helps small New York insurance agencies connect day-to-day IT management with cybersecurity, vendor oversight, and compliance operations. We can help assess the technology around your AMS, implement practical safeguards, and organize the documentation that supports your program. Pickard Solutions does not provide legal advice or certify legal compliance.

Learn more about our IT and cybersecurity services, or schedule a cybersecurity readiness review.