FinCEN’s 2016 cyber advisory tied SAR decisions to intrusion facts and set no new staffing duty
FinCEN’s October 25, 2016 advisory said cyber-events aimed at transactions could require suspicious activity reports, with technical details. That decision turned on intrusion facts, yet its FAQs said no new staffing or cybersecurity knowledge was required of AML units.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
FinCEN’s October 25, 2016 advisory said cyber-events aimed at transactions could require suspicious activity reports, with technical details. That decision turned on intrusion facts, yet its FAQs said no new staffing or cybersecurity knowledge was required of AML units.
- The week The advisory covered four topics.
- The trigger: from intrusion to suspicious transaction The advisory read cyber-events into that rule.
- The content: what the SAR should carry That applied beyond cyber-events.
- The handoff: from the security team to the filer The advisory’s third section addressed collaboration.
- The outside channels: other institutions and authorities The advisory’s fourth section addressed sharing among institutions.
- How the advisory reached different institutions A large bank with a security operations center and a financial intelligence unit had the people.
- Objections, in order The advisory said it changed no obligations. [1] But it explained that cyber-events aimed at transactions are reportable attempts and that SARs should carry cyber information. [1] An institution that had treated intrusions as purely a security matter would need to change its workflow to meet existing rules as FinCEN explained them.
- What a BSA officer and a security leader could check together The two teams can agree when detection of facts occurs for SAR timing purposes, with counsel’s advice.
- With hindsight FinCEN returned to cyber reporting in later advisories.
The week
On October 25, 2016, the Financial Crimes Enforcement Network issued Advisory FIN-2016-A005, titled Advisory to Financial Institutions on Cyber-Events and Cyber-Enabled Crime. [1] FinCEN said it issued the advisory to help financial institutions understand their Bank Secrecy Act obligations regarding cyber-events and cyber-enabled crime. [1]
The advisory covered four topics. They were reporting cyber-enabled crime and cyber-events through suspicious activity reports, and including cyber-related information such as IP addresses with timestamps, virtual-wallet information and device identifiers. [1] They also included collaboration between BSA/AML units and in-house cybersecurity units, and sharing information among financial institutions. [1]
The advisory named its audience. It said it should be shared with cybersecurity units, network administrators, risk departments, fraud prevention units, BSA/AML management, AML intelligence units and AML analysts and investigators. [1]
It defined three terms. A cyber-event was an attempt to compromise or gain unauthorized electronic access to electronic systems, services, resources or information. [1] Cyber-enabled crime was illegal activity, such as fraud, money laundering or identity theft, carried out or facilitated by electronic systems and devices. [1] Cyber-related information described technical details of electronic activity, such as IP addresses, timestamps and indicators of compromise. [1]
The advisory stated its limits. It said it did not change existing BSA requirements or other regulatory obligations. [1] It said filing a SAR does not relieve an institution of other requirements to notify regulators of events concerning critical systems or disruptions in its ability to operate. [1] It said the Cybersecurity Act of 2015 did not change SAR reporting requirements, SAR confidentiality rules or section 314 safe harbor protections. [1]
Its core guidance concerned mandatory reporting. A financial institution must report a suspicious transaction conducted or attempted by, at or through it that involves or aggregates to $5,000 or more. [1] If an institution knows, suspects or has reason to suspect a cyber-event was intended to conduct, facilitate or affect a transaction, the advisory said, the event should be considered part of an attempted suspicious transaction. [1]
The advisory gave three examples of mandatory reporting. One was a malware intrusion that put $500,000 of customer funds at risk. [1] Another exposed customer account data and credentials useful for transactions. [1] The third was a denial-of-service attack at a money services business that distracted staff from stopping an unauthorized $2,000 wire. [1] In each case the advisory explained why a SAR was required. [1]
FinCEN also encouraged, but did not require, reports of egregious, significant or damaging cyber-events that did not otherwise require a SAR. [1] Its example was a denial-of-service attack that disabled online banking for a significant period without affecting any transactions. [1]
The same day, FinCEN published nine frequently asked questions to supplement the advisory. [2] It said they superseded FAQs on computer intrusion published in 2001. [2] The answers covered what cyber information to include, how to complete SAR fields, cumulative SARs, scanning and probing, and unsuccessful events. [2] Two answers said the advisory created no new requirement for BSA/AML units to have cybersecurity staff or knowledge. [2]
FinCEN’s cyber advisory of October 25, 2016 said it created no new obligations. [1] It explained how the existing suspicious activity rules applied to cyber-events. The explanation had an operational consequence the advisory itself described. Whether a cyber-event required a SAR depended on what the institution knew about the event’s intent, targets and the funds at risk. [1]
In our reading, those facts usually sat with the security team, while the decision and the filing sat with the BSA/AML unit. The advisory encouraged the two to collaborate. [1] The FAQs published with it said FinCEN did not require AML units to have cybersecurity personnel or knowledge. [2]
Our argument is that the advisory rested a legal decision on facts held by one team, while the duty to file stayed with another. The workforce question that raised was left to each institution. We take the advisory in four parts:
- The trigger: when a cyber-event becomes a reportable suspicious transaction.
- The content: what cyber-related information a SAR should carry.
- The handoff: how the facts move from the security team to the team that files.
- The outside channels: sharing with other institutions and notifying authorities.
The parts do not overlap. The first is the legal test, the second the report’s content, the third the internal workflow and the fourth the external flows. After them, we look at how the advisory reached different institutions, take the objections in order, and end with what a BSA officer and a security leader could check together today.
This is a reading of public documents, not legal advice. Institutions should confirm their obligations with counsel.
The trigger: from intrusion to suspicious transaction
The rule the advisory applied
The bank SAR rule requires reporting of a transaction conducted or attempted by, at or through the bank that involves or aggregates at least $5,000 in funds or other assets. [3] The bank must know, suspect or have reason to suspect one of the conditions the rule lists, such as funds derived from illegal activity. [3]
The advisory read cyber-events into that rule. A cyber-event intended, in whole or in part, to conduct, facilitate or affect a transaction should be considered part of an attempt to conduct a suspicious transaction. [1] Events that could affect transactions would be reportable because they are unauthorized, relevant to a possible violation of law and regularly involve efforts to acquire funds illegally. [1]
In our reading, this is the advisory’s central move. An intrusion that has not yet touched an account can still be an attempted transaction, if its purpose was to reach funds.
The facts that decide it
The advisory told institutions what to weigh. They should consider all available information about the cyber-event, including its nature and the information and systems targeted. [1] To determine the amount, they should consider in aggregate the funds and assets involved in or put at risk. [1]
Each of those facts comes from an investigation. What systems the attacker reached, what data was exposed, what the malware was built to do. Those are findings of a security team or an outside forensic firm. A BSA analyst reading an alert queue would usually not have them.
The three examples
The advisory’s first example was a malware intrusion. After detection, the bank determined the event put $500,000 of customer funds at risk, based on the systems and information targeted. [1] It reasonably suspected the intrusion was meant to enable unauthorized transactions, so it must file. [1]
The second example exposed sensitive customer information, such as account numbers, credentials, PINs and challenge answers. [1] The institution reasonably suspected the event targeted that information to conduct transactions of at least $5,000, for instance by selling it to other criminals. [1] It should file. [1]
The advisory noted that in both examples no actual transaction may have occurred. [1] The suspicion rested on the circumstances of the event and the systems and information targeted. [1]
The third example involved a money services business. A denial-of-service attack distracted staff from stopping an unauthorized $2,000 wire. [1] The institution should file one SAR covering both, because the attack was used to conceal the wire. [1] FinCEN noted that the money services business threshold is, with one exception, $2,000. [1]
Proceeds as well as targets
The advisory described two ways cyber-events touch funds. Some target funds directly, as in fraud, credential theft and misappropriation. [1] Others generate illicit proceeds, as in ransomware attacks and the sale of stolen proprietary information and card numbers. [1]
The second kind matters for institutions that never suffer the attack. A bank whose customer pays a ransom, or whose account receives proceeds from stolen card data, may see the money without seeing the intrusion. The facts then come from the transaction side, and the security team may have nothing to add.
The older intrusion category
The advisory kept an existing category in place. It said guidance on reporting unauthorized electronic intrusions remained unchanged, and that cyber-events meeting that definition should be reported as such. [1]
It set out the definition. An intrusion means gaining access to a financial institution’s computer system for one of three ends. [1] They are affecting funds of the institution or its customers, taking critical information including customer account information, or damaging, disabling or disrupting critical systems. [1] The third limb reaches events with no link to funds at all. In our reading, that made some purely disruptive events reportable under the older guidance, whatever the new test said.
Unsuccessful events
The FAQs closed a possible gap. They said an otherwise reportable cyber-event should be reported regardless of whether it was successful. [2] The test was whether the institution knew, suspected or had reason to suspect the event was intended to or could affect a transaction. [2]
That answer widened the security team’s role. A blocked attack leaves evidence of intent: the target, the payload, the commands. Whether that evidence pointed at funds was again a security finding.
Scanning and probing
The FAQs drew a line on routine activity. They said institutions are not required to file a SAR for continuous scanning or probing of systems or networks. [2] FinCEN said filing on each scan would be impractical and could detract from efforts against more significant threats. [2]
Institutions could include scanning information in a SAR on a reportable event, where relevant. [2] That gave the security team a clear floor. Background noise is not a SAR. A targeted event aimed at funds may be.
Voluntary reports
The advisory encouraged voluntary reports of egregious, significant or damaging cyber-events that did not otherwise require filing. [1] Its example was a denial-of-service attack that disabled online banking for a significant period and could not have affected transactions. [1]
FinCEN said SAR reporting of cyber-events, even those below the mandatory standard, is highly valuable in law enforcement investigations. [1] A voluntary report is a judgment call, and the facts that inform it, such as the attack’s scale and source, are again held by the security side.
The clock
The bank SAR rule sets the timing. A bank must file no later than 30 calendar days after initial detection of facts that may constitute a basis for filing. [3] If no suspect was identified on the date of detection, it may delay up to an additional 30 calendar days to identify one, but no more than 60 calendar days after initial detection. [3]
For a cyber-event, initial detection of facts may happen in the security operations center. In our reading, if the facts that may constitute a basis for filing are first known to the security team, the clock may start there. Institutions should confirm with counsel how their own procedures treat that point.
The content: what the SAR should carry
Complete and accurate reports
The advisory said institutions are required to file complete and accurate reports that incorporate all relevant available information, including cyber-related information. [1] It said everyday transactions increasingly rely on electronic systems, so illicit activity has a digital footprint. [1]
That applied beyond cyber-events. Institutions should include available cyber-related information when reporting any suspicious activity, such as fraudulent wire transfers. [1] The FAQs gave the example of IP addresses and timestamps for a fraudulent wire, even with no cyber-event involved. [2]
The list of information
The advisory listed what a SAR involving a cyber-event should include, to the extent available. [1] The list ran from the description and magnitude of the event to its known or suspected time, location and signatures. [1] It continued with indicators of compromise, relevant IP addresses and timestamps, device identifiers, methods used and other relevant information. [1]
The FAQs gave a longer, non-exhaustive list. [2] It covered source and destination information, such as IP address and port with timestamps in UTC, URLs, attack vectors and command-and-control nodes. [2] It covered file information, such as suspected malware filenames and MD5, SHA-1 or SHA-256 hashes. [2] It also covered e-mail and social media names, registry modifications, indicators of compromise, CVEs and involved accounts, including virtual currency accounts. [2]
Where it goes on the form
The FAQs explained how to place the data. Specific SAR fields existed for IP addresses, website addresses and e-mail addresses. [2] Information without a field belonged in the narrative. [2] Filers could attach a single CSV file with patterns of online activity in tabular form, but the attachment was not a substitute for the narrative. [2]
The FAQs asked for consistent terminology. They said filers should use widely used and accepted terms, and pointed to NIST’s glossary of information security terms. [2] For characterization, filers should tick all applicable boxes, such as unauthorized electronic intrusion or account takeover, and use the Other field where none fit. [2]
Cumulative SARs
FinCEN recognized the volume problem. The FAQs said filing a SAR for each cyber-event may require significant time and resources. [2] An institution may file a single cumulative SAR for multiple cyber-events that are too numerous to report individually and are similar or related. [2]
The FAQs limited this. Cumulative SARs were for cyber-events, not other suspicious activity, which must follow normal procedures. [2] The advisory gave the example of one SAR reporting several malware intrusions sharing methods, vulnerabilities and IP addresses. [1]
Why investigators wanted it
The advisory explained the value of the information. It said FinCEN and law enforcement regularly use BSA reports to start investigations, identify criminals and disrupt networks. [1] It said law enforcement had used reported IP addresses with timestamps, cyber-event data and virtual-wallet information to track criminals, identify victims and trace funds. [1]
It gave one example. BSA reporting by more than 20 financial institutions played an important role in investigating an internet-based company that acted as an unregistered money transmitter offering anonymity. [1] FinCEN said criminals used the company for over $6 billion in illicit transactions. [1]
The example shows why the content mattered. An IP address with a timestamp in one SAR can link to the same address in another institution’s SAR. A narrative without it cannot be linked that way.
Times and formats
The FAQs asked for IP address and port information with timestamps in UTC. [2] That detail matters more than it looks. Security logs and banking systems may record time in different zones. A SAR that mixes them can mislead an investigator matching events across institutions. Agreeing on UTC in the handoff form removes one source of error. [2]
Who can produce the content
The content list reads like an incident report. Hashes, command-and-control nodes, registry changes and CVEs are produced by security tools and analysts. [2] A BSA analyst could transcribe them. Transaction monitoring systems generally do not produce them.
The advisory said it did not create any new obligation or expectation to collect cyber-related information as a matter of course. [1] It asked for what was available. In our reading, that meant the content of a cyber SAR depended on what the security team recorded and passed on. If the security team kept no structured record, there would be little to report.
When the software lags
The advisory addressed a technical constraint. If an institution’s filing software could not yet include certain cyber-related information, it should file discrete SARs manually until it updated its software, as FinCEN had clarified in May 2013. [1] That is an operations detail with a staffing cost: manual filings take analyst time.
The handoff: from the security team to the filer
What the advisory encouraged
The advisory’s third section addressed collaboration. It said collaboration and ongoing communication among BSA/AML, cybersecurity and other units would help institutions conduct a more comprehensive threat assessment. [1] Institutions were encouraged to share relevant information internally, including with BSA/AML staff, cybersecurity personnel and fraud prevention teams. [1]
It described the benefit in both directions. Cybersecurity information could reveal patterns and identify suspects not known to BSA/AML units. [1] BSA/AML units could use cyber-related information, such as the timing of events and transaction instructions coded into malware, to identify suspicious activity and understand their risk exposure. [1] Cybersecurity staff could use BSA/AML information to guard against attacks. [1]
The advisory linked this cooperation to complete SAR reporting and to a strong culture of compliance. [1]
What the FAQs said was not required
Two FAQs set the boundary. Question 7 asked whether FinCEN now required BSA/AML units to have personnel or systems devoted to cybersecurity. The answer was no. [2] Question 8 asked whether BSA/AML personnel were now required to be knowledgeable on cybersecurity. The answer was no. [2]
The FAQs said there were no new requirements, and that a BSA/AML unit may work with its institution’s cybersecurity personnel as necessary to identify and report suspicious activity. [2]
The gap between the two
Read together, the advisory and the FAQs leave a gap. The legal test depended on cyber facts. [1] The filing unit did not have to understand them. [2] The bridge between the two was collaboration, which was encouraged and not required. [1] [2]
In our reading, that structure avoided imposing a staffing mandate through an advisory, which said it changed no obligations. [1] The effect was to leave the design of the handoff to each institution.
Who owns the decision
The advisory left ownership open, but the SAR rule does not. The duty to file sits with the bank. [3] Who acts for it is set by the institution’s own program. In our reading, a sound design keeps the decision with the BSA officer and makes the security team accountable for the facts.
That split has a practical test. If the BSA officer cannot explain a decision not to file a cyber-event, the facts were not good enough or did not arrive. If the security team cannot show what it sent, the handoff was informal. Either gap is visible in a review of a few recent incidents.
What a working handoff needs
A handoff that works has a trigger, a form and an owner. The trigger tells security staff which events to send. The form tells them what to send. The owner on the BSA side decides whether to file and records the decision.
The advisory supplies material for each. Its test of intent to affect transactions is a trigger. [1] Its list of cyber-related information is a form. [1] [2] Its call for collaboration names the units involved. [1] It does not say who owns the decision. That is the institution’s choice.
A hypothetical flow at a community bank
A hypothetical community bank shows the handoff in miniature. Its managed security provider detects a credential-stealing malware infection on a teller workstation. The provider’s ticket goes to the bank’s information security officer.
Under the advisory, the question is whether the bank has reason to suspect the event was intended to affect transactions of at least $5,000. [1] The officer reviews what the malware targeted and which systems the workstation could reach. If it could reach wire initiation, the facts point toward a SAR. [1]
The officer completes a short form with the fields the FAQs list: the malware filename and hash, the command-and-control address, the time in UTC and the accounts reachable. [2] The BSA officer reads the form, decides and records the decision. The 30 calendar day period runs from initial detection of facts that may constitute a basis for filing. [3]
Every step in that flow depends on the provider’s ticket containing the right facts. If the ticket says only malware removed, the BSA officer has nothing to weigh.
Training both sides
Training follows from the handoff. Security staff need to know the advisory’s test well enough to recognize when an event may concern funds. [1] BSA staff need to read a technical form well enough to judge it. [2] Neither needs to become the other. The FAQs said BSA staff are not required to be knowledgeable on cybersecurity. [2] Recognizing a trigger and reading a form is a smaller skill.
Records of the handoff
The bank SAR rule requires a bank to keep a copy of any SAR filed and the original or business record equivalent of any supporting documentation for five years from filing. [3] It says supporting documentation is deemed filed with the SAR. [3]
For a cyber SAR, the supporting documentation may include the security team’s incident record. In our reading, that brings the handoff form inside the BSA record-keeping regime once a SAR is filed. Security teams should know their notes may become part of a SAR file, and write them accordingly.
The language problem
The two teams speak different languages. Security staff describe events in terms of systems and techniques. BSA staff describe them in terms of transactions, subjects and typologies. The FAQs asked filers to use widely accepted terminology and pointed to NIST’s glossary. [2] That request is also a training need.
A short glossary shared by both teams, built from the FAQs’ list, would reduce translation errors. [2] It is the kind of document a workforce plan can produce without new hires.
Confidentiality inside the institution
SAR confidentiality limits who may know a SAR was filed. The advisory said the Cybersecurity Act of 2015 did not change SAR confidentiality rules. [1] A handoff design therefore needs care. Security staff send facts to the BSA unit. They may not need to learn whether a SAR resulted.
That asymmetry can frustrate a security team that wants feedback. A program can give feedback on the quality of what was sent without disclosing filing decisions. Institutions should check the design with counsel.
Capacity and cost
Collaboration has a cost. Security analysts spend time packaging facts for a SAR. BSA analysts spend time reading technical material. FinCEN acknowledged the cost of individual cyber SARs when it allowed cumulative filing. [2]
For a small institution, the same person may cover parts of both roles, or both may be outsourced. The advisory applied regardless of size. [1] The FAQs’ statement that no new staffing was required protected small institutions from a mandate, and left them to find their own route to the facts. [2]
The outside channels: other institutions and authorities
Sharing under section 314(b)
The advisory’s fourth section addressed sharing among institutions. Section 314(b) of the USA PATRIOT Act provides a safe harbor from liability for institutions that, after notifying FinCEN and meeting other requirements, share information to identify and report possible money laundering or terrorist activity. [1]
The advisory said institutions may share cyber-related information under section 314(b) for those purposes and receive its safe harbor protections. [1] Its examples were malware signatures, IP addresses, device identifiers and virtual currency addresses. [1]
The FAQs added that any participating institution, such as a bank, may share with any other participating institution, such as a card operator or money transmitter. [2] They listed benefits, including alerting other institutions about customers whose credentials may have been compromised. [2]
What 314(b) sharing requires internally
Section 314(b) is a BSA tool, available after notice to FinCEN. [1] Cyber indicators come from security work. Sharing cyber information under the safe harbor therefore needs the same handoff as SAR filing, in the other direction. [1] [2]
The advisory also noted the Cybersecurity Act of 2015 as a separate route. It said that law authorizes non-federal entities to share defined cyber threat indicators and defensive measures for cybersecurity purposes. [1] An institution could have two sharing programs, run by different teams, under different legal bases.
Notifying regulators
The advisory said a SAR does not relieve an institution of any other requirement to notify appropriate regulators of events concerning critical systems and information, or of disruptions in its ability to operate. [1] It pointed to existing guidance, including OCC and FRB, FDIC and NCUA guidance on reporting computer-related crimes. [1]
That sentence separated two duties. A SAR goes to FinCEN. A regulator notice goes to the supervisor. The two can concern the same event and be prepared by different people on different clocks.
Calling law enforcement
The advisory told institutions needing immediate help after a cyber-event or cyber-enabled crime to contact the appropriate regulatory and law enforcement agencies. [1] It referred to a DHS fact sheet on threat and asset response and a Justice Department guide to agencies to contact. [1]
The bank SAR rule adds a duty for urgent cases. In situations needing immediate attention, such as ongoing money laundering schemes, the bank shall immediately notify an appropriate law enforcement authority by telephone, in addition to filing a SAR. [3] A security team handling an active intrusion aimed at funds may be the first to know that a case needs that call.
Examiners and supporting documents
The bank SAR rule says supporting documentation must be made available on request to FinCEN, to law enforcement and to federal regulators that examine the bank for BSA compliance. [3] A security incident record kept as supporting documentation could therefore be read by an examiner or an investigator. [3] That is one more reason the record should be accurate, dated and free of speculation presented as fact.
Four channels, one event
A single intrusion could therefore produce a SAR to FinCEN, a 314(b) exchange with another institution, a notice to a regulator and a call to law enforcement. [1] [3] Each channel had its own owner, clock and content. The advisory described each. It did not merge them.
How the advisory reached different institutions
Large banks
A large bank with a security operations center and a financial intelligence unit had the people. Its challenge was the interface: a defined route from security findings to SAR decisions, and a shared vocabulary. [1] [2] The cumulative SAR option addressed the volume such a bank might face. [2]
A large bank also runs several sharing programs at once. Its 314(b) exchanges, its threat-sharing memberships and its law enforcement contacts may each sit with a different team. [1] Mapping them against one incident shows where the same indicator is handled twice, or not at all.
Community banks and credit unions
A community bank or credit union might rely on its core processor or a managed security provider for monitoring. The facts the advisory made decisive could sit outside the institution. [1] The handoff then ran through a contract. An institution in that position would need its provider to report events in enough detail to support the SAR test.
The advisory listed NCUA guidance on reporting computer-related crimes among the existing guidance it referred to. [1] The 2025 FAQs list NCUA’s rule, 12 CFR 748.1(d), alongside the bank rule. [6] Credit unions should confirm the details with counsel.
Money services businesses
The advisory’s third example was a money services business, with a $2,000 unauthorized wire. [1] FinCEN noted that threshold applies, with one exception, to money services business SARs. [1] A money transmitter with online channels could face events like the advisory’s example, and the lower threshold brings more of them into scope.
Broker-dealers and other filers
The advisory cited the SAR rules for each type of financial institution by section. [1] The 2025 FAQs list those rules by name, including brokers or dealers, mutual funds, insurance companies, and futures commission merchants and introducing brokers. [6] A broker-dealer with online accounts faces the same test for account takeover attempts aimed at moving assets. Its AML and security functions would need the same handoff.
Service providers
Core processors, payment processors and managed security providers were not addressed by name in the advisory. They hold facts their customers need. Whatever the customer’s SAR decision, the provider’s incident records would be its raw material.
Objections, in order
1. The advisory changed nothing, so the workflow did not change
The advisory said it changed no obligations. [1] But it explained that cyber-events aimed at transactions are reportable attempts and that SARs should carry cyber information. [1] An institution that had treated intrusions as purely a security matter would need to change its workflow to meet existing rules as FinCEN explained them.
2. Security teams should not drive SAR decisions
In our reading, they need not decide; the BSA unit can. But the decision depends on facts the security team produces. [1] Without a defined handoff, the BSA unit decides on whatever it happens to hear.
3. AML staff cannot be expected to learn security
The FAQs agreed they were not required to. [2] The objection supports the argument. If the filing unit need not understand the facts, the institution needs a translator role, a shared glossary or a structured form that carries the meaning across. [2]
4. Cumulative SARs make volume manageable
They help. [2] They do not reduce the need to sort reportable events from scanning and from non-reportable incidents. That sorting is a security task with a legal consequence.
5. Regulator notification covers the same ground
It covers a different ground. The advisory said a SAR does not relieve an institution of other notification duties. [1] The reverse also holds in our reading: a notice to a regulator is not a SAR. The two duties need their own owners.
6. Voluntary reporting invites noise
FinCEN encouraged voluntary reports only for egregious, significant or damaging events. [1] It told institutions they need not file on routine scanning and probing. [2] The noise concern is answered by those limits. The harder cases are the ones in between, where the security team’s judgment about significance decides whether a voluntary report is made.
7. FinCEN should have required collaboration
There is a case for a mandate. A required handoff would have set a floor for every institution. But FinCEN issued an advisory, which it said did not change obligations. [1] A mandate would have needed a different instrument. Within the tool it chose, encouragement and clear examples were what it could offer.
What a BSA officer and a security leader could check together
The trigger list
A joint list of event types that the security team sends to the BSA unit, built on the advisory’s test of intent to affect transactions, sets the starting point. [1] It should cover unsuccessful events, which the FAQs said remain reportable when the test is met. [2]
The handoff form
A form based on the FAQs’ list of cyber-related information gives security staff a template. [2] It should record the systems and data targeted and the funds at risk, the facts the advisory said to weigh. [1]
The clock
The two teams can agree when detection of facts occurs for SAR timing purposes, with counsel’s advice. The rule’s 30 calendar day period runs from initial detection of facts that may constitute a basis for filing. [3]
The sharing route
The BSA unit’s 314(b) registration and the security team’s threat-sharing memberships can be listed side by side. [1] The list shows which indicators go where, and under which legal basis.
The notice map
Finally, a map of all four channels for a single event, SAR, 314(b), regulator and law enforcement, with an owner and clock for each, turns the advisory’s separate statements into one procedure. [1] [3]
Feedback on quality
A program can review a sample of handoff forms for completeness against the FAQs’ list, without disclosing filing decisions to the sender. [2] The review shows which fields are missing and whether training is working.
Provider terms
Where monitoring is outsourced, the provider agreement can require incident records with the fields the handoff form needs. [2] That keeps the facts the advisory made decisive inside the institution’s reach. [1]
With hindsight
FinCEN returned to cyber reporting in later advisories. On November 8, 2021, it issued FIN-2021-A004, an advisory on ransomware and the use of the financial system to facilitate ransom payments. [4] FinCEN said it was updating and replacing its October 1, 2020 ransomware advisory. [4]
The 2021 advisory repeated the 2016 content standard. It said institutions are required to file complete and accurate reports that incorporate all relevant available information, including cyber-related information. [4] It asked that SARs involving cyber events, including ransomware, include cyber-related information and technical indicators in the form and narrative. [4]
It also asked filers to use a key term, CYBER-FIN-2021-A004, in SAR field 2 and the narrative, and to select SAR field 42 for a cyber event. [4] Its list of intended readers included AML/BSA departments, legal departments, and cyber and security departments. [4] In our reading, FinCEN again addressed both teams in one document.
The federal banking agencies added a separate notification duty. On November 23, 2021, the OCC, the Federal Reserve Board and the FDIC published a final rule on computer-security incident notification, effective April 1, 2022, with compliance from May 1, 2022. [5] It requires a banking organization to notify its primary federal regulator of a notification incident as soon as possible and no later than 36 hours after determining that one has occurred. [5]
The rule also covers bank service providers. A provider must notify affected banking organization customers as soon as possible after determining that an incident has caused, or is reasonably likely to cause, a material service disruption or degradation for four or more hours. [5] That gave institutions relying on providers a defined flow of facts from them, though for regulator notice rather than for SARs. [5]
The rulemaking drew on SAR data. The agencies said they reviewed supervisory data and SARs involving cyber events against banking organizations in 2019 and 2020 to estimate notification incidents. [5] They estimated approximately 150 annually and said an analysis of SAR filings would not capture the full scope of incidents the rule addressed. [5] In our reading, the cyber information the 2016 advisory asked for had become an input to later rulemaking.
On October 9, 2025, FinCEN and the four federal banking and credit union agencies issued FAQs on suspicious activity reporting requirements. [6] They said there is no requirement or expectation under the BSA for an institution to document a decision not to file a SAR. [6] They said institutions are not required to conduct a separate review after filing a SAR to determine whether activity continued. [6]
The 2025 FAQs said they did not alter existing BSA requirements or establish new supervisory expectations. [6] In our reading, that answer covers a decision not to file after a security investigation of a cyber-event, as checked on November 16, 2026. [6] Institutions may still choose to record such decisions as a matter of internal control.
What held up from 2016 was the reporting standard. FinCEN’s later ransomware advisory used the same language about complete reports with cyber-related information. [1] [4] What stayed open was the workforce question. No document in our sources required a defined handoff between security and BSA teams; the 2016 FAQs’ answer that no new staffing was required has not been replaced in our sources. [2] [4] [6]
Spotted an error? Tell us and we will check it and correct the article where needed.