KMS Financial Services Inc. (2021): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
KMS Financial Services Inc. disclosed the incident on 30 Aug 2021. What was exposed, as the sources state it: The SEC states personally identifying information of approximately 4,900 customers and clients was exposed. The ledger reads the access path as stolen user credentials and session tokens.
Open the ledger · Report a correction
- Disclosed
- 30 Aug 2021
- Incident window
- September 2018 to December 2019
- Cloud or provider
- not public
- What was exposed
- The SEC states personally identifying information of approximately 4,900 customers and clients was exposed.
- How access was gained
- The SEC states the cloud-based email accounts of 15 financial advisers or their assistants were taken over by unauthorized third parties. The SEC order finds the firm did not adopt written policies requiring additional firm-wide security measures until May 2020 and did not fully implement them firm-wide until August 2020. The press release does not name the email provider or state how the accounts were taken over.
- Access path
- Stolen user credentials and session tokens
- Kind of control that addresses it
- require phishing-resistant multifactor authentication on every cloud-hosted email account and block legacy sign-in methods that bypass it
In the words of the source
“between September 2018 and December 2019, cloud-based email accounts of 15 KMS financial advisers or their assistants were taken over by unauthorized third parties” (regulator filing, SEC press release 2021-169: SEC Announces Three Actions Charging Deficient Cybersecurity Procedures)
Primary sources
- regulator filing: SEC press release 2021-169: SEC Announces Three Actions Charging Deficient Cybersecurity Procedures, dated 30 Aug 2021
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- SEC press release 2021-169: SEC Announces Three Actions Charging Deficient Cybersecurity Procedures, read 16 Nov 2026
Last reviewed 16 Nov 2026.