
IRS e-file account security is not a single setting you turn on. Tax professionals must protect Electronic Filing Identification Number (EFIN) access, keep their IRS e-file application information accurate, safeguard taxpayer data, and maintain a written information security program where applicable. In 2026, the practical baseline is unique user access, multi-factor authentication (MFA) wherever the IRS system supports it, strong account recovery controls, documented procedures, staff training, and a tested response plan for suspicious activity.
IRS Publication 3112 is the IRS guide for becoming and remaining an authorized e-file provider. It requires providers to protect their EFIN and related credentials from unauthorized use and to report changes that affect their application information. Your EFIN is an authorization identifier, not a shared office login.
Quick Answer
IRS e-file providers should limit EFIN and e-services access to authorized people, use individual accounts instead of shared credentials, promptly remove departed staff, and protect taxpayer information under IRS guidance. A written information security program, documented access reviews, MFA, secure endpoints, and an incident plan help reduce the risk of unauthorized filing activity and taxpayer-data exposure.
Two numbers that shape the risk
Start with the IRS rules that apply to your firm
The IRS publishes several documents that work together. Publication 3112 covers the IRS e-file application, suitability process, EFINs, responsible officials, and provider responsibilities. Publication 4557 gives tax return preparers security guidance for protecting taxpayer data. Publication 5708 explains the security expectations for tax professionals and discusses a written information security plan.
The Federal Trade Commission (FTC) Safeguards Rule can also apply to professional tax preparation firms because they handle customer information as financial institutions under the rule. The FTC's Safeguards Rule guidance describes requirements such as a written security program, a qualified individual, risk assessment, safeguards, service-provider oversight, and incident-response planning. Whether a particular requirement applies to your structure is a legal and compliance question to review with counsel.
For a working explanation of these operational duties, see our guide to tax safeguard compliance 4557.
How to secure IRS e-file access in your office
Assign named owners and users
Identify the responsible official, each person who can access IRS systems, and the business owner responsible for approving access changes.
Use individual accounts and MFA
Do not share passwords, recovery email accounts, mobile numbers, or authenticator devices. Turn on MFA for IRS and connected business systems when available.
Review access at defined times
Check access before tax season, after staff or vendor changes, and after any suspected compromise. Disable access immediately when it is no longer needed.
Document and test your response
Record who contacts the IRS, clients, insurers, counsel, and technology providers if you suspect account misuse or taxpayer-data exposure.
Protect the account around the IRS portal
A firm can follow IRS portal instructions and still create risk through the systems surrounding the account. An attacker who gets into a preparer's email, password manager, workstation, or phone number may be able to reset accounts, impersonate staff, or search for taxpayer records.
Use access controls that are easy to audit
- Give every employee a separate work email and separate application accounts.
- Require MFA for email, tax software, cloud storage, remote access, and password-manager access.
- Use a password manager so staff can create long, unique passwords without storing them in browsers, notes, or spreadsheets.
- Restrict EFIN-related records and taxpayer documents to staff who need them for their role.
- Keep an access-change log that shows who approved new access and when former access was removed.
The NIST password guidelines 2026 guide can help you set a password policy that emphasizes unique passwords, password managers, and phishing-resistant sign-in methods where available. Pair that policy with the role-based controls in our tax-firm access control guide.
Important
Do not treat a legitimate-looking IRS, tax-software, or document-sharing email as proof that it is safe. IRS Publication 4557 warns tax professionals about phishing and other attempts to obtain taxpayer information. Verify unexpected requests through a known phone number, bookmarked portal, or established vendor contact.
Make your written security plan usable during tax season
A written information security plan, often called a WISP, should connect your policy to actual office behavior. It should identify the taxpayer data you hold, the systems that store or transmit it, the people responsible for safeguards, the risks you have assessed, and the controls you use to address those risks. It also needs a process for staff training, vendor review, access changes, backups, and incident response.
Do not file a WISP away as a template. Review it after a material change, such as opening another location, adopting new tax software, adding a managed service provider, or changing how remote staff access client data. Firms with more than one office should define who can grant access and who reviews alerts centrally. Our guide to multi-location tax office centralized security management explains why that ownership matters.
If you need a starting point, review the practical WISP requirements first. Bellator also offers a custom WISP starting at $749 for up to 5 users, with a custom quote for larger practices. For a small firm, a tailored plan can reasonably avoid 20 to 40 billable hours of assembling, adapting, and organizing documentation, but it does not replace the firm's responsibility to follow and review the plan.
Your IRS e-file account security check
Tap each step as you finish it. Your progress is saved on this device.
0 of 5 done
What to do if you suspect unauthorized access
Act quickly, preserve evidence, and avoid making assumptions about what an alert means. Change exposed credentials from a known-clean device, revoke active sessions where the affected service supports it, document the time and indicators you observed, and contact your technology provider or incident-response resource. Your reporting obligations can depend on the facts, contracts, insurance policy, and applicable law, so involve counsel when appropriate.
The IRS provides reporting channels and instructions for suspected tax-related identity theft and e-file concerns. Start with the IRS's current Identity Theft Central resources, then follow the escalation procedures in your firm's WISP. For prevention, train staff on the patterns behind phishing attacks on tax professionals, especially credential-reset lures and fake document-sharing notices.
The practical standard for 2026
For most tax firms, the best next step is not a new product. It is confirming that named people, protected accounts, documented procedures, and monitored devices match the way your office actually works. That creates evidence you can review, makes staff changes safer, and gives you a clearer starting point if something goes wrong.
Book a Free Tax Cybersecurity Assessment
Get plain-language help choosing what fits your situation. No pressure.
Frequently Asked Questions
Use MFA wherever the relevant IRS or connected business system offers it. IRS access methods and enrollment options can change, so confirm the current sign-in requirements in the IRS portal and official guidance before relying on a particular method.
An EFIN is tied to an authorized e-file provider, while individual IRS and business-system credentials should be assigned to named people. Shared logins make it harder to investigate activity, remove access promptly, and show that access was controlled.
Many tax firms need a written information security program under the FTC Safeguards Rule and IRS security guidance. The exact application of requirements depends on your firm and services, so use IRS and FTC guidance and seek legal advice for legal questions.
Include immediate containment steps, internal decision owners, technology and insurance contacts, evidence-preservation steps, client-communication approval, and a process for determining reporting obligations with counsel. Keep the plan accessible even if your normal systems are unavailable.
From requirement to defensible practice
Turn IRS and FTC expectations into a WISP your office can follow
A useful compliance path makes the obligation clear, identifies the evidence to retain, and connects written policy to the safeguards used every day.
People also look for
Keep exploring Tax security & WISP
Understand what tax professionals need to document, protect, and prepare before an IRS or FTC review.
- Common question: free WISP templateStart with a written information security planUse a practical WISP framework built around the safeguards tax practices need.
- Common question: IRS Publication 4557 requirementsRead the Publication 4557 guideSee how the IRS expects tax professionals to safeguard taxpayer data.
- Common question: IRS WISP requirementsReview the WISP requirementsWork through the required sections and the evidence your practice should retain.
- Common question: FTC Safeguards Rule checklistUse the FTC Safeguards checklistTranslate the rule into a clear list of security and documentation tasks.
- Common question: tax practice incident response planPrepare a tax-office incident planKnow who to contact, what to preserve, and how to respond to a client-data incident.



