MTradecraft: Cybersecurity Compliance Tradecraft for SEC and FINRA Registered Investment Firms
Picture
  • Home
  • SEC and FINRA Services
  • Chief Hacking Officer
  • Red Team
  • Penetration Testing
  • Threatwire Articles
    • The SEC OCIE Cybersecurity Observations Decoded
    • The SEC and Cybersecurity Documentation
    • The Dark Web and Advisory Firms
    • DIY Guide to SEC and FINRA Cybersecurity Vulnerability Scanning
    • The Biggest Cybersecurity Mistake
    • Hackers and Remote Workers
    • A Criminal's Retirement Plan
    • Home Security System Hacking
    • IT Asset Inventory
  • Schedule a Meeting

9/18/2020

Internal vs External Vulnerability Scanning:Why you need both.

0 Comments

Read Now
 

​The Ins and Outs of Vulnerability Scanning

Picture
If you’re an RIA or hedge fund tackling SEC/State-board cybersecurity compliance, you’re likely to hear the word “scan” from your IT department or cybersecurity consultant.
​

In our conversations with firms, we often find that there is an expectation for a single scan that will satisfy their SEC cybersecurity requirements. For most firms however, there is actually a requirement to conduct several separate scans: some scans come from inside the network(i.e., an “internal scan”) and some scans come from the outside the network (i.e., an “external scan”).


In this post I’ll cover the differences between these two types of scans, including how they’re performed, the types of vulnerabilities they seek out and why they’re necessary.


For the purpose of this article I’ll be referencing SEC cybersecurity guidelines; though you will find FINRA and the state-boards generally require the same assessments.


The idea is that you want to spot security vulnerabilities within your business network and applications by:


Running internal and external network vulnerability scans at least annually and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades, hiring/firing employees, etc)


Internal and external vulnerability scans are conducted in a similar manner. Both scans are administered via a computer program called a scanner. However, that doesn’t mean there is one program that can simultaneously conduct both scans. An external vulnerability scan looks for holes in your network firewall(s), intrusion detection systems, modems, and routers, where malicious outsiders can break in and attack your network.


By contrast, an internal vulnerability scan operates inside your business’s firewall(s)to identify real and potential vulnerabilities inside your business network. For instance, unpatched operating systems and misconfigured remote desktop applications.


Why Both Scans are Critical to Your Investment FirmImagine your firm as a house in which a couple and their child reside. The doors and windows are locked to keep intruders from getting inside, but one day the child lets a stranger in the back door while the parents are out working in the front yard. The stranger quietly rummages through the house looking for valuables, gathers them up and throws them out an upstairs window.


Hackers and malware aren’t just present outside your firewall; they can be on the inside as well. The idea that threats may originate from the internet makes sense to most, but what are less commonly understood are threats originating from within the internal network. These types of threats can include disgruntled employees who have targeted systems from the inside, or malware (such as viruses or Trojans) that is downloaded onto a networked computer via the Internet or a USB stick. Once the malware is on the internal network, it sets out to identify other systems and services on the internal network—especially services it would not have been able to “see” from the Internet.


So according to the house example above, an external scan would check to be sure all doors and windows of the house are locked and impassable, while an internal scan would search the inside of the house to ensure that the family’s valuables are hidden from plain sight and properly secured.



Share

0 Comments

8/17/2020

Video:   More DIY Cybersecurity Tips

0 Comments

Read Now
 

More Cybersecurity DIY Tips for RIAs, Hedge Funds, and Family Offices

In this video, we review some methods that firms can use to develop their SEC required cybersecurity documentation.

We will cover:
-Vendor Due Diligence
-IT Asset Inventory and Checklist
-Internal Network Map Building
-External Domain Map Building

Share

0 Comments

8/5/2020

Secure Remote Access For RIAs and Hedge Funds

0 Comments

Read Now
 

Secure Remote Access:
Why It’s Important and How Your Investment Firm Should Do It Right

COVID-19 forced SEC and FINRA registered firms to transition their employees to a work-from-home policy. BCPs were put to the test in real life.


Why Remote Access Is Necessary for RIAs and Hedge Funds.
These seems pretty obvious.  The world is closed but markets are still open. IT Administrators are under increasing pressure to provide access to individuals who can’t access firm assets physically. Remote access is especially concerning for those of you who have custody of physical access or connections to trading platforms capable of making trades.



How to Ensure Secure (Secret) Remote Access to Your Firm's Critical Infrastructure.

RIAs and Hedge Funds should lay the groundwork for secret remote access by not enabling remote access by default. This means that firms need to view remote access as the exception, not the rule. 


Those working to ensure secure remote access should consider leveraging guidance such as NIST SP 800-82.  These standards can help firms designate which systems need remote and how to secure that access with 2 factor authentication (2FA).

2FA is the biggest deal here! 

Use it or lose it!



I don't care if you use RDP or Teamviewer or RealVNC.  USE 2FA.  It solves a lot of problems.


Share

0 Comments

7/28/2020

How to Steal Assets from an Investment Advisor

0 Comments

Read Now
 

How to Steal Assets:
A Hacker's Retirement Plan

All day you show people how to retire.

Task 1. Work Hard
Task 2. Save your money.

Criminals do it different.

Task 1. Let others work hard.
Task 2. Steal others retirement funds from their financial advisor.

In this webinar, I will demonstrate how hackers go after RIAs, Family Offices, and Hedge Funds to steal client assets. I think that when you see how these attacks unfold from an attacker's perspective you will be more aware of your own vulnerabilities.

Share

0 Comments

7/28/2020

Video: The IT Asset Checklist

0 Comments

Read Now
 

The SEC and FINRA say you need an IT Asset Checklist.

This is how you do that with ease.

The SEC / FINRA and State Boards say you need to make an IT inventory list as part of your cybersecurity compliance protocols. You have a couple of options to do this.

1. Open Word Doc and Start Typing (Hard and Time Consuming)
2. Download FINRA Template and Start Typing (Easy and Time Consuming)
3. Use Zenmap to do it for you (Very Simple, Free, Comprehensive and takes Seconds)

#3 is as simple as Simon can make it.

Any questions?

Here is a video to show you how to do it.

Share

0 Comments

7/28/2020

Video: The DIY Guide to Cyber Security

0 Comments

Read Now
 

The DIY Cybersecurity Webinar for RIAs, Hedge Funds, and Family Offices

Back in January 2020, the SEC's OCIE office released their Cybersecurity Observations paper.

As per usual, it was filled will all the same copy-and-paste bullshit that we have all been accustomed to reading when the SEC starts talking cybersecurity. The SEC can't protect their own network, so why should we expect any useful tips from them on how to protect your firm’s networks? In this webinar, I will dissect their report, piece by piece, and demonstrate what you need to be doing to meet your compliance obligations and defend against attackers.

Warning: This will be technical, so bring your geekiest employee.


Share

0 Comments

7/28/2020

Video: The Dark Web and Investment Firms

0 Comments

Read Now
 

The Dark Web and Advisory Firms

Their research begins with OSINT (Open Source Intelligence) to scope out targets. We will take a look at the Dark Web and how hackers use past breach data and stolen credentials to target your firm. Hackers are looking for "low hanging fruit" and easy targets by looking for firms with little to no security measures in place.

This webinar will give you insight into how you can prevent your firm from being that low hanging fruit.


Share

0 Comments

7/28/2020

The SEC's Ransomware Alert

0 Comments

Read Now
 

SEC RISK ALERT:
Cybersecurity and Ransomware

Share

0 Comments

7/15/2020

VPNs: What do they do, and what don't they do?

0 Comments

Read Now
 

VPNs: What Do They Do, and What Don’t They Do?

I don't have the time or the patience to discuss every detail of VPN's in this article, but I can definitely fill you in on what you need to know.

Quick answer: You need one.

Why?

They create privacy when transmitting data Every time you connect to send data through the internet (ie visiting Google or sending an email) you are transmitting data over the public Internet. It is like driving a car; you are using public roads. A VPN “tints the windows,” so as you data travels along "public highways", a hacker/snooper can not see what the data consists of. That data is encrypted by the VPN. This is especially important if you connect to things like Hotel Guest Wifi Networks or Starbucks Wifi networks.

It hides your location – A VPN routes traffic in a different way and some services can help you fool the destination about your location.  For example, I connect to a US VPN when I am in Costa Rica so that I can still watch "The Americans". That title isn't available in Costa Rica.  I think because the US government fears it will give Costa Rican's ideas about spy on America for Costa Rica.  But I could be wrong.

Control your employees and protect you data (just like the SEC tells you to do). 
If a VPN is required to connect an employee to your server then the CCO can also cut him off from network access immediately in the event that employee gets canned.  Unauthorized connections from former employees can easily be controlled with the click of a mouse.

Now, Im sure that all sounds great.  But let's talk about the shit that a VPN can't do  and set the record straight.

It will not prevent you from being hacked.
For instance, if you are using Office365 and your password is "Password" then I am getting in.  No VPN is going to prevent that.  Hell, I might even get in if you use a complicated password like "Pa55word".  A VPN won't fix stupid.

It will not prevent you from being phished. 

It will not improve speed or network performance. 
In fact, you will probably notice a slight bottleneck.  For me, the security benefits far out-weight this problem.

It won't protect you from insider threats.  Your stupid employees are still going to act stupid...even with a VPN.  When you give someone VPN access to the network, you are giving them the keys to the caste.  Make sure you trust them.

I hope that helps.  In the past I have used PIAVpn, ExpressVPN, and NordVPN.  I have had success with all three of those.  Currently I use ProtonVPN which has been my favorite.  And full disclosure, no-body paid me to say that shit.  I am just sharing my experience.

I hope that helps.


Share

0 Comments

1/13/2020

A Phishing Story: How to Steal $400MM from an RIA

0 Comments

Read Now
 

In Search of Fidelity:
A Successful Phishing Transcript


I was recently hired by "Carlson Wealth" to perform a penetration test against their RIA.  The main priority was to discover sensitive/leaked data and to determine if it would be possible for an outside attacker to gain access to the PMS system so that theoretically we could affect trades/cashiering/etc. 

It should terrify you how easy it is. 

I went down the phishing route because I had already located a username and password that one of the firm’s employees used to access their custodian.  The username and password I collected was accidentally published publicly due to a misconfigured Office365 setting and a careless CCO. That is not uncommon. Additionally, the same username and password had already been published on the DarkWeb, so this was a highly sensitive area that I needed to investigate further because the same credentials were used for her email.

The usernames/pass was also tied to a rolling 2 factor authentication code that I need to access the PMS system – so that is what I went after.

It took less that 40 minutes to get access by phishing a firm employee.

(Shortened for readability. The firm and employees names have been changed to protect the guilty. I also bought Sharon lunch for having used her like I did. She was pretty upset that she had been so easily conned into giving away the keys to the kingdom.)

----------------------------
Call #1 -
I called Sharon @ Carlson as “Dave White”

Dave – Hi Sharon – I am interested in opening an account with you folks. If I do, where do you keep my money.

Sharon – We use Fidelity as the custodian for our accounts.

Dave – Ah! Fidelity! I already have an account with them, so great. My current advisor uses them, so will it be an easy transition if I move my accounts? Since the accounts are already there, how do I switch them over to be managed by your firm?

Sharon – It is pretty easy. I will send you some paperwork to fill out and then I will fax those up to Fidelity.

Dave – Excellent! And in the mean time I can email you my PDF statement so that you can get the ball rolling with onboarding

Here, I am setting Sharon up to open a PDF containing key-logging malware that I will send her if need to get access that way. At this point, I am still not sure how I am going to get into the system so I am planting this seed. This is a great option as I have yet to have an advisor not open a malicious PDF when they think there is inbound assets coming.

Sharon – Sound great. My email address is……….

Dave – Great. I will send that over soon.

Now, I must do some more research to figure out how I will get in.  So I call another advisor that is completely unrelated to the firm.
---------------------------------------
Call #2 –
I called ABC Wealth Management ..another firm that I found uses Fidelity so that I can get some background information on how Fidelity operates.

The phone was answered by a young lady named Allison.

Dave – Hi Allison you might not be the right person and I am sorry for the distraction, but I am hoping you can help me out. I am a movie director and I am working on a film and I am needing someone to interview for my project. The film involves an investment firm that experiences a cyber attack and looses the clients money. I need someone’s expertise to make sure my movie fits the real life scenario since I know little about cybersecurity. I know you are very busy, but would you perhaps have a few minutes to answer some simple questions for my project?

Allison– Sure, I would love to help. What kinds of questions do you have?

Dave – Well, I know what it means to balance a portfolio. That means sometimes you have to sell some holdings and buy others to make the portfolio balance. I get that. But what I don’t understand is HOW do you make the trades in those portfolios.

Allison– Well...it’s really not that complicated....


(Allison goes on for 15 minutes telling me everything I need to know about how she uses Fidelity’s Wealth Central system. She explained how they access the portfolios, how they access the systems, how they open new accounts, their reports, how they protect the information using 2fa, what kind of 2fa they use...everything. I lead her along with questions and I didn't ask any personal or firm related questions to keep her from getting suspicious. After taking detailed notes on Fidelity, it was time to call Sharon back.
-------------------------
Call #3 –
I called Sharon once more.
This time as Chris Johnson, a customer service rep from Fidelity’s Wealth Central asking Sharon if she had a few minutes for a survey.

Chris - Hi Sharon – This is Chris Johnson with Wealth Central. I am conducting a customer satisfaction survey and wanted to see if you had 2 minutes to answer some questions about your satisfaction with our service. We are sending all respondents a coupon for a free lunch at Chick-fil-A.  Would it be OK if I ask you a few questions?

Sharon was happy to help…and sounded excited for the break in her routine.

Chris - First off, are you authorized on the Wealth Central Program?

Sharon - Yes.

Chris – Great!
Okay, what hours are you guys in the office?

How many employees dial into Fidelity?
How often to do call us?
Is there anyone in particular you like to talk to?

Did we ever fail to meet your expectations?
How is our response time?
Do you have any suggestions on how we can improve?

Sharon answers them all.

Chris: Thanks, Sharon. I really appreciate your help and your time. Let me save your answers real quick.

Chris – (Pausing….) Hmm...that is interesting.  Are you an authorized employee who can talk about your experience.

(Asked in a puzzled/questioning way, because victims are always happy to provide clarity or prove themselves right. It blinds them when you ask them to prove themselves)

Sharon– Yes, I am authorized on all accounts.

Chris – OK, that is strange because I don’t see your name listed on the account.

Sharon(acting somewhat insulted)– What! I have been here for 7 years and call Fidelity everday!

Chris – No doubt. This is a frequent problem and one of the side-reasons for my call. I want to make sure we have the most accurate records. Give me one second to get you added here.

(20 second delay….lots of typing in the background that Sharon can hear)

Ah yes….I see your authorization paperwork right here. Sharon Smith. I found it.  No problem. Let me get you added to the official record again. I'm not sure how it was removed because I see where you were authorized previously.  Can you please read me the current 6 digits from your 2FA device so that I can authenticate you are who you say you are?  With all the cybersecurity scares today, they make me authenticate everyone!

Sharon reads the digits as I type them into my login screen.

Chris - Sharon....can I tell you something secret?

Sharon - Yes?

Brian - This is Brian Hahn.

Sharon - (10 Second Pause to realize what just happened)  Shit.

The pentest is now over as I have gained full admin control of the entire firm’s $450MM portfolio in less than 40 minutes.

Sharon knew I was performing a pentest on her firm that month because she sat in during the initial meeting.  This firm also gets a A+ for their compliance cybersecurity training that they do quarterly....yet I couldn't have had an easy time phishing the firm's most confidential data in a matter of minutes.

Stay Vigilant! 





Share

0 Comments

11/7/2019

How To Properly Secure your Network Wifi Router

0 Comments

Read Now
 

There is no easy way to say this...

Your router sucks.

That is especially true if you are using a router supplied by your ISP.  Get rid of it.  Now.

If you already have a decent router in place, go through this checklist to make sure you have it hardened correctly.

​
  1. Change the default password and user id. The new one should be at least 16 characters long. No common words used as passwords.  Use common password hygiene.
  2. Turn off WPS.  Huge vulnerabilities here.
  3. Turn off UPnP.  
  4. Turn off NAT-PMP options.
  5. Wi-Fi encryption should be WPA2 with AES.
  6. Wi-Fi passwords should be strong and secure.  Use proper password hygiene.  
  7. Don’t use an SSID {Wifi Network Name} that identifies you. (ie.  ABCWealthWifi)
  8. Use a password protected Guest Network. Use it for guests and IoT devices. Never allow guests on the biz side of your network.
  9. Turn Off Remote Administration.  
  10. Test for open ports. Nmap is free and does the job excellently. Find em and shut'em down.
  11. Turn off Port forwarding...if you can.
  12. Check for new firmware monthly.
  13. Get rid of the ISP provided equipment. It is vulnerable. (Did I say that already?  It is important)
  14. Change the DNS servers that your router gives out to attached devices. ISP assigned DNS servers are usually the default, and worst, option. Use DNS servers are 9.9.9.9 (from Quad 9, backed up by 149.112.112.112) and 1.1.1.1 (from Cloudflare backed up by 1.0.0.1).
  15. Change the LAN side IP address of the router.  Don't use manufacture defaults.
  16. For routers with a web interface, lock down access to the router from the LAN side with 2fa.
  17. Turn off Ping reply.
  18. Turn off wireless networks when not in use. Have a procedure to shut it down when you go home at night.  Many wifi routers have a physical On/Off button.
  19. Block the ports used by Windows file sharing.
  20. Block network printers from making any outbound connections.
  21. If the router can send email when certain error or security concern occur, use it.
  22. Test your router with Shodan and a Censys.io query to see what you see.


That should get you started.  



Share

0 Comments

10/29/2019

The Ultimate Guide to Using Firefox Securely

0 Comments

Read Now
 

A Step by Step guide to hardening Firefox.
​

This guide shows a user in an easy-to-follow way how to improve the privacy and security settings of Firefox, which, when combined with a privacy VPN, gives a user a strong framework for protecting their firm and client's information.

This guide is broken down into sections, each addressing different areas of security and privacy settings within Firefox. It should also be noted that these settings will break some websites, especially the components that block scripts. These problems will improve over time as the sites that you routinely visit will be fixed by your settings changes in the recommended plugins. Some websites are enemies of privacy and will not be usable securely or privately due to security flaws that break functionality or intentional blocking by the websites that cannot track you.

Also, when Firefox installs updates, it is common for some of these settings to revert back to their defaults. When Firefox notifies you that it has updated, it is a good idea to review this guide again and make sure that no settings have changed. This page will also be routinely updated with the latest information, so it is good to check this page for updates.

Section 1: Privacy Add-ons/Extensions for Firefox 

Block ads with uBlock Origin – Not to be confused with uBlock, uBlock Origin is a powerful ad-blocking tool that prevents most types of ads from appearing in your browsing or streaming. Unlike Adblock Plus and other alternatives, uBlock Origin does not have a whitelist and universally blocks all of the ads that it can. It is crucial to block ads because it is a common vector for both surveillance and malware.

Block much more with uMatrix – uMatrix is a powerful and script, cookie, and cross-site request blocker. It can recognize and block tracking through media and image files, and gives you granular control over what you allow and what you disallow on a per-site basis. It is important to block scripts and XHR requests as they are the most common attack vectors for malware and intrusion. Their is an easy uMatrix guide here!

Block behaviorally with Privacy Badger – extensions like Disconnect and others block cookies by comparing the cookies to known ones. The EFF’s Privacy Badger blocks cookies by tracking their behavior rather than comparing them to repositories. This allows Privacy Badger to actively block new threats as they appear, even with no frame of reference to work from.

Make sure your web is encrypted by default with HTTPS Everywhere – While the web is increasingly encrypted by default thanks to Let’s Encrypt, many sites are still unencrypted or running both encrypted and unencrypted content, either out of laziness or error. HTTPS everywhere makes sure that all of the requests coming from your browser request SSL encryption, so that if it is available, it is used by default.

Check your work with Firefox Lightbeam – Once you’ve made the changes in this guide, you can check the impact of your changes using Lightbeam. Lightbeam monitors the requests that are made when you are visiting a website and gives you a visual layout so that you can see where your data is going.

Section 2: Options in Firefox to Improve Security and Privacy

General – No Major Changes
The built in Firefox spell checker operates using local language libraries that are built into the browser. This means that your keystrokes and what you write are not uploaded to Mozilla or any 3rd party by the spellchecker. Do note that websites can disable the built-in spell checker and use their own, like gmail. This means when you are on websites you should be aware that your keystrokes within that page can always be recorded by the site and/or any 3rd party scripts running on that site.

Home – New Windows and Tabs Should be Blank Pages – Disable All “Home” Checkboxes
Having a homepage that is not a blank page allows the site in question to know every time you’ve opened Firefox or started a new tab.

Pocket is a semi-controversial system that is built into Firefox that attempts to give users a relevant homepage without receiving any data from the user. It works by Firefox downloading a list of high quality articles from pocket servers daily, and then locally, pocket compares your browsing history against the list of articles to make relevant recommendations. This allows Mozilla to push relevant content to users without ever seeing their browser history. It also has a “sponsored article” system that shows paid-for articles alongside the high quality content. The criticisms of the system are that Mozilla gets to decide what is high quality content and what is not, and that this a way to get ads (paid content) on a user’s home page by default. While pocket doesn’t pose any blatant security or privacy risks and it is open-source, I recommend disabling it for performance reasons as well as the criticisms above.

Search – Change the default search engine to DuckDuckGo – Disable Suggestions
DuckDuckGo is a private search engine that does not store or cache user results. This means that your searches remain private and are not traded or sold for marketing or surveillance purposes. Because of the non-invasive approach of DuckDuckGo, some focused searches may not give you the most relevant results. To fix this, you can use a feature called Bangs to have DuckDuckGo redirect your search to another engine like Wikipedia or Startpage in a private way. For Startpage you do this by preceding your search in the navigation bar with a !sp. For example, if I wanted to search for information on Alabaster and use Startpage through DuckDuckGo,

I’d type:
!sp Alabaster

And I’d get a private Google search result from Startpage.

Search Suggestions is a feature that tries to predict what you’re typing in the search bar and provide you with relevant results before you finish typing out your search. It does this by analyzing your keystrokes in real-time through an interactive service. This means that the search provider is getting all of your information on keystrokes that type into the bar as soon as you hit the spacebar, not when you complete typing your search. This isn’t a huge privacy concern unless you leave a non-private search engine as your default.

Privacy and Security
Do not save passwords or autofill – Both of these store information that can be exfiltrated from you.

Do Not Store History as it can be pulled by plugins and shared.
​
Do not allow 3rd party cookies as these are nearly exclusively used for tracking.
You should leave first party cookies enabled because this gives you the option of allowing a cookie for a specific site with the uMatrix plugin. This corrects a lot of site-breaking issues for sites that you frequently visit in which specific cookies are okay.

Do not allow any suggestions in the search bar, as these broadcast your activity to 3rd parties.

Tracking protection can be enabled, but it is handled by addons as well, so it is redundant.

Block popups because not only are they annoying, but also because they are a common method of delivering malware payloads through malicious pages.
You want Firefox to warn you when sites try to install addons, as these have all kinds of security and privacy consequences.

Accessibility services are typically used in surveillance plugins for corporate networks and privacy unfriendly addons for Firefox, they should be disabled.
Do not share telemetry data with Mozilla.

On Blocking Dangerous and Deceptive Content – There is some false information circulating around in other guides about how this feature works in Firefox due to confusion about Google’s SafeBrowsing initiative. Google has two different methods of doing safe browsing, one is private and one is not. The Lookup API is the non-private method of checking URLs. This sends queries to Google servers every time you browse to a site to check if they are “safe.” This essentially hands Google all of your browsing information. The second, safer method is called the Update API. This stores a list of unsafe sites and domains locally, and you download a list from Google periodically that updates this list of domains. This method does not give Google any information from the user and it is what Firefox uses. You DO NOT need to disable this feature for privacy reasons and it does generally boost your security by checking your browsing against the blacklisted sites.

Special Section for Trusted Root CAs
This section is revisited in detail at the end of this article.

Firefox Account
Synchronizing your account across multiple devices has multiple privacy and security risks that should be avoided. Do not sign in to a Firefox account.

Section 3: Advanced privacy and security improvements with about:config settings changes

Firefox is highly configurable for privacy, and to access hundreds of advanced settings, you type about:config into the navigation bar where you normally type web addresses.

You will see a warning telling you to be careful! It is a warning worth heeding as setting things up incorrectly can make your browser crash or cause all kinds of issues. Misconfiguration can require a full reset of browser settings that will make you have to start over the process of hardening your browser.

The changes below are designed to significantly reduce the number of methods that websites can profile your activity. Why each setting is selected to be changed is included in the description of the setting.

Disable WebRTC – WebRTC is a protocol related to digital rights management that helps content websites track users. It has the capability to give up your real IP address even while connected to a VPN or Tor.

To disable WebRTC, in the search bar type media.peerconnection.enabled and double click on the setting to change it to false. This disables WebRTC.

Enable Fingerprint Resistance – This setting actually manages many behaviors in Firefox, it is a group of settings that are used by the Uplift project (a sub-project of Tor) to make the browser ignore most types of fingerprinting requests.
To enable Fingerprint Resistance – Type privacy.resistfingerprinting into the search bar and double click on the setting to set it to “true.” This hardens the browser against most types of fingerprinting.

Disable the 3DES cipher – This setting allows the 3DES cipher, which has multiple known security weaknesses. It needs to be disabled.
To disable 3DES – Type security.ssl3.rsa_des_ede3_sha into the search bar, and double click on the setting to set it to “false.” This prevent 3des from being supported.

Require Safe Negotiation – This setting is for preventing a serious code injection attack related to how clients and servers negotiate which encryption settings to use. This setting forces only safe negotiation methods to be used.
To enable Require safe negotiation – Type security.ssl.require_safe_negotiation into the search bar, and double click the setting to set it to “true.” This prevents this code injection attack from working.

Disable TLS versions 1.0 and 1.1 – Transport Layer Security (TLS) is a protocol created by industry consensus for creating secure connections between web resources and applications. The current standard version of TLS is 1.2 and version 1.3 is rapidly being adopted at the time of this writing. TLS version 1.0 and 1.1 (1.0 esecially) have some known flaws with negotiation and cryptography in certain situations, and should be disabled for security reasons.

To Disable TLS 1.0 and TLS 1.1 – Type security.tls.version.min into the search bar, and double click on the setting. In the box that pops up, type 3 and hit okay. This will force Firefox to only use TLS 1.2 and TLS 1.3.

Disable 0-RTT – Zero Round Trip Time Resumption (0-RTT) is a feature that is new in TLS 1.3 that allows a client and server to negotiate a connection with fewer steps, allowing https websites to load more quickly. There are two problems with this. First, in order to do this you lose forward secrecy (generating a new key for every session and throwing away the key when the session is over). Secondly, 0-RTT requires special implementation in order to prevent replay attacks, which some web developers will certainly fail to protect from. Disabling 0-RTT enhances security and privacy.
To Disable 0-RTT – Type security.tls.enable_0rtt_data into the search bar, and double click on the setting to set the feature to false. This will force full secure negotiation for all connections made by Firefox.

Disable Automatic Formfill – Formfilling requires that information be cached in the browser, this can include valuable information like usernames and passwords and the information can reference visited sites even with history disabled.
To Disable Formfill – Type browser.formfill.enable into the search bar, and double click on the setting to set the feature to false. This will prevent Formfill from caching any information about your browsing.

Disable All Disk Caching – Websites can write temporary information to hard drives such as access tokens, security keys, browsing data, secure scripts, and more. This information is usually deleted after a secure session is terminated, however, deleted information is trivially recoverable if it is not overwritten. Complicated firmware and drivers for flash memory based devices like SSDs introduce features like wear leveling that hide components of the storage from the OS entirely, making it very hard to verify that deleted information is actually deleted in an unrecoverable way.
To Disable all Disk Caching – Type browser.cache into the search bar. This will pull up many settings. Look for these specific settings: browser.cache.disk.enable and double click to set it to false, browser.cache.disk_cache_ssl and double click to set it to false, browser.cache.memory.enable and double click it to set it to false, browser.cache.offline.enable and double click it to set it to false, browser.cache.insecure.enable and double click it to set it to false. This will disable all types of disk caching in Firefox.

Disable Geolocation Services – Geolocation services are bad for privacy for obvious reasons. You don’t want people lasering on your exact location.
To Disable Geolocation – Type geo.enabled into the search bar, and double click the setting to set it to false. This will prevent geolocation services from working. (Note: WebRTC should also be disabled as mentioned above, as it uses a different method of generating location data.)

Disable Plugin Scanning – Plugins can query what extensions and plugins that you have installed on Firefox to profile users. Disabling this feature improves both privacy and functionality while browsing privately.
To Disable Plugin Scanning – Search for plugin.scan.plid.all and double click the setting to set it to false. This will disable the feature.

Disable ALL Telemetry Features – These are features that explicitly collect data.
To Disable All Telemetry – Type “telemetry” into the search bar. A large number of settings will pop up in the search. Search for the following and set them all to false:
browser.newtabpage.activity-stream.feeds.telemetry browser.newtabpage.activity-stream.telemetry
browser.pingcentre.telemetry
devtools.onboarding.telemetry-logged
media.wmf.deblacklisting-for-telemetry-in-gpu-process
toolkit.telemetry.archive.enabled
toolkit.telemetry.bhrping.enabled
toolkit.telemetry.firstshutdownping.enabled
toolkit.telemetry.hybridcontent.enabled
toolkit.telemetry.newprofileping.enabled
toolkit.telemetry.unified
toolkit.telemetry.updateping.enabled
toolkit.telemetry.shutdownpingsender.enabled
These changes prevent all kinds of metadata from being stored about your connection both locally and by Mozilla.

Disable Prefetching – Firefox by default will pre-load all linked pages on pages that you visit. This becomes a privacy issue because this leads to your browser broadcasting a list of the links that are on the page you are currently visiting, which can allow outside parties to profile your browsing habits from your DNS traffic, or, if you’re not on a VPN it can allow your ISP to infer what web pages you visit within secure sites by looking at the prefetch resources.

To Disable DNS Prefetching – Type network.dns.disableprefetch into the search bar and double click on the option to set the option to True. This will prevent the browser from broadcasting your browsing habits through DNS requests. You also need to disable network.prefetch-next

To Disable Network Prefetching – Type network.prefetch-next into the search bar and double click the option to set it to false.

Disable Referral Headers – Websites use referral headers to track users movements from one site to another. This tells the website you are visiting what site that you came from. To Disable HTTP Referral Headers – Type network.http.sendRefererHeader into the search bar and double click the setting which will open a dialog box. Type 0 into the box that pops up and hit okay to completely disable Referral headers.


Disable WebGL – WebGL is an application interface that allows websites direct access to your graphics card. This introduces a huge attack surface for potential security risks as well as unique types of fingerprinting. It should be disabled.
To Disable WebGL –  Type webgl.disabled into the search bar, and double click on the option that is displayed to set it to true.


Disable Battery API – The Mozilla API can allow a site to track the current battery life of a device, which can be used in conjunction with other methods to identify and track users. To Disable the Battery API – Type dom.battery.enabled into the search bar and double click the option listed to set it to false.

Disable web handshakes that re-use credentials – (more info: SuperCooKeys)

Disable Session Identifiers (HIDDEN FEATURE)
To disable session identifiers: Type about:config into your navigation bar in Firefox, in the screen that pops up, you must right click on a blank area of the page and select new -> boolean.

In the window that pops up, we have to enter the exact name of the hidden feature: security.ssl.disable_session_identifiers and hit OK.

Then we have to search for the feature that we added and make sure that it is set to TRUE.

Enable First-Party Isolation
This feature prevents the browser from making requests to sites outside of the primary domain from the site. This prevents large ubiquitous services from following your keys around the web like a supercookie, and it also prevents all kinds of 3rd party data tracking.To enable first party isolation: Type about:config into your navigation bar in Firefox. In the screen that pops up, enter privacy.firstparty.isolate into the search bar, and make sure that the setting is set to TRUE. (This setting can break websites that rely heavily on 3rd party libraries and scripts.)

Disable TLS False Start
This is because it does not allow the client to fully complete its handshake before starting the actual session. There is more info here from the IETF: https://tools.ietf.org/html/rfc7918#section-4 (See section 5. Security Considerations)
To disable TLS false start: Type about:config into your navigation bar in Firefox. In the screen that pops up, enter security.ssl.enable_false_start into the search bar, and make sure that the setting is set to FALSE.

About Camera and Microphone Access – There are many settings in Firefox related to access to the Camera and Microphone. Recently, Firefox has implemented a number of good security and privacy features surrounding access that make editing these settings unnecessary. Disabling these features in about:config will disable Mic and Camera access globally, rather than allow you to permit access to services that you want (like Jitsi Meet for audio/video chat).
If you NEVER want to use a microphone or webcam through your browser, you can manually disable access. Otherwise, you should allow your permissions built into Firefox to manage access.


Section 4: Editing Trusted Certificate Authorities

This step takes some trial and error, but dramatically helps reduce your attack surface by outside parties.

First, we need to discuss how the certificate system works. Certificates around the web tell your browser if a site is genuine and they are managed by a group of “root certificates” from organizations around the world. These organizations vouch for the security of their own root certificate and vouch for the validity of all certificates that are made from it. This means that when Typhoon (fake name used for example) creates a certificate for a website, they are telling your browser “this site is genuine because Typhoon says it is.” You are relying on the reputation of Typhoon to keep your browser safe from spoofing.

There’s some inherent problems with this system. How do we know that Typhoon’s security standards are perfect? How do we know that Typhoon would never create an invalid certificate for someone else accidentally? How do we know that Typhoon would never create a fake certificate for a law enforcement agency or spy organization?

Therein lies a large problem. Firefox (and all browsers and operating systems) trust hundreds of these root certificates by default, and for most users around the world, you don’t encounter most of these root certificates in your day to day web use.

You can remove many of these root certificates from Firefox to make it so that you trust far fewer authorities. To access the certificate manager, you go to the settings menu in Firefox, and click on the Privacy and Security pane on the left side. Then you scroll to the bottom of the page and click on “View Certificates…” In the window that opens up, you can scroll through all of the possible certificate authorities and remove trust (by clicking on the Delete or Distrust… button) from all of the authorities for sites that you do not visit or do not trust for ethical reasons.

This step does require some research, you have to find out which certificates are used by the sites you visit, and limit your trusted certificates to those. Also, many of the big American certificate authorities (such as the Amazon Root CAs, DigiTrust, RapidSSL, GeoTrust, GlobalSign) will break a majority of the Internet if you mistrust them.

Personally I tend to mistrust all certificates from languages that I do not speak (which means it is unlikely that i’ll ever run into those certificates around the web) and also eliminate any certificates that cater to local regions such as Taiwan, Switzerland, the Netherlands, etc.

If you accidentally mistrust a certificate that you want to trust once again, you can click on the “edit trust” button in the certificate manager window, and check the boxes for the services that should trust this certificate authority.​

------------------------------------------------------------------------

The folks over at PIA VPN wrote this awesome framework on how to harden Firefox and make it as safe as possible.  We have use PIA VPN for several years and it is a company that we recommend for our clients.  Their service and pricing is top notch and their technology is very user friendly.  PIA's VPN service is one of the most cost effective cybersecurity tools you could possible implement. 

We are not affiliated with or compensated by PIA (or any other company).  We just believe in their product.



Share

0 Comments

10/9/2019

Battle Story: How I hacked an RIA owner's webcam and watched his wife fold laundry.

0 Comments

Read Now
 
I want to share a quick story from a pen-test I did today because this should terrify you. 

Often times I find interesting vulnerabilities so I wanted to share them with you because I think the idea of what goes on during a pentest is often nebulus to a firm's owner and CCO.  I think the extent of understanding what can be exploited is also lost.

The Client:  $1.6B SEC Registered RIA in Los Angeles.  15 employees.  2 custodians.

The Vulnerability:   I was able to take control of the RIA owner's home surveillance system (16 different internal cameras) and gained admin access to his security system.  I was able to watch his wife fold laundry in the living room. I did ALL of that without ever once having to enter a password.

How did I do it?  Check out the video below.

My thoughts: Penetration testing isn't just for regulatory compliance.  Often times, we are able to catch these major privacy vulnerabilities before others do.  These tests are about protecting your privacy and protecting your client's data.

Share

0 Comments

8/12/2019

Don't believe your RIA/BD/Tech Provider.  Here is why they are not protecting your network

0 Comments

Read Now
 

Do you think your BD, RIA, or cloud is protecting your clients? 

Think again....
​

Not a day goes by where I don't hear some form of the statement: "My BD/RIA/Cloud Storage Provider/Custodian/Landlord/girlfriend  provides all of our cybersecurity needs." 

Unfortunately, many firms are mislead with statements from these providers and they believe their clients are protected.

You can ask yourself these two simple questions to know if you are fully protecting your clients and meeting your compliance obligations:

1.  Do they send you the audit reports each time they do a vulnerability scan?  If the SEC or FINRA comes knocking, you are expected to have the documentation ready.  Curious what documentation they request?  Read here. 
As the old saying goes, "If it isn't documented, it didn't happen."

2. 
Does your service provider scan your local network for vulnerabilities and provide a vulnerability assessment report at least annually?  I didn't think so.  If they aren't providing these scans, how do you expect to produce the documentation needed for an exam?

This quick video describes why you might not be protected like you thought you were.



Share

0 Comments

7/30/2019

Steps to Safeguard Against Ransomware Attacks

0 Comments

Read Now
 

Steps to Safeguard Against Ransomware Attacks
​

Original release date from CISA: July 30, 2019

The Cybersecurity and Infrastructure Security Agency (CISA), Multi-State Information Sharing & Analysis Center (MS-ISAC), National Governors Association (NGA), and the National Association of State Chief Information Officers (NASCIO) have released a Joint Ransomware Statement with recommendations for state and local governments to build resilience against ransomware:
  1. Back up systems—now (and daily). Immediately and regularly back up all critical agency and system configuration information on a separate device and store the backups offline, verifying their integrity and restoration process. If recovering after an attack, restore a stronger system than the one lost, fully patched and updated to the latest version.
  2. Reinforce basic cybersecurity awareness and education. Ransomware attacks often require the human element to succeed. Refresh employee training on recognizing cyber threats, phishing, and suspicious links—the most common vectors for ransomware attacks. Remind employees of how to report incidents to appropriate IT staff in a timely manner, which should include out-of-band communication paths.
  3. Revisit and refine cyber incident response plans. Have a clear plan to address attacks when they occur, including when internal capabilities are overwhelmed. Make sure response plans include how to request assistance from external cyber first responders, such as state agencies, CISA, and MS-ISAC, in the event of an attack.
​
CISA encourages organizations to review the Joint Ransomware Statement and the following ransomware guidance:
  • MS-ISAC Security Primer on Ransomware
  • CISA Tip Sheet on Ransomware
  • NGA Disruption Response Planning Memo
  • NASCIO Cyber Disruption Planning Guide

Share

0 Comments

7/16/2019

Tips for Detecting Phishing

0 Comments

Read Now
 

Tips for Detecting Fishing

Share

0 Comments

7/16/2019

What compliance documentation does the SEC or FINRA require of registered firms?

0 Comments

Read Now
 

Cybersecurity Compliance Documentation for RIAs, IBDs, and Hedge Funds.

Link to most updated version of this document

This is a pastedump of different questions we have seen FINRA/SEC examiners send firms before showing up for an onsite interview.


All questions have been Copied and Pasted Directly from SEC and FINRA requests.  They are not organized in any particular fashion (yet….) If you have any you would like to add to this list, please send me an email
---------------------------------------------------------------------------------------


​F
or each of the following practices employed by the Firm for management of information security assets, please provide the month and year in which the noted action was last taken; the frequency with which such practices are conducted; the group with responsibility for conducting the practice;
and, if not conducted firmwide, the areas that are included within the practice. Please also provide a copy of any relevant policies and procedures.


• Physical devices and systems within the Firm are inventoried.
• Software platforms and applications within the Firm are inventoried.
• Maps of network resources, connections, and data flows (including locations where customer data is housed) are created or updated.
• Connections to the Firm’s network from external sources are catalogued.
• Resources (hardware, data, 2 factor-authentication,  and software) are prioritized for protection based on their sensitivity and business value.
• Logging capabilities and practices are assessed for adequacy, appropriate retention, and secure maintenance.


------------------------------------------------------------------------------
Please provide a copy of the Firm’s written information security policy and employee usage agreements.


------------------------------------------------------------------------------
Please indicate whether the Firm conducts periodic risk assessments to identify cybersecurity threats, vulnerabilities, physical vulnerabilities and potential business consequences.  If such assessments are conducted: a. Who (business group/title) conducts them, and in what month and year was the most recent assessment completed? b. Please describe any findings from the most recent risk assessment that were deemed to be potentially moderate or high risk and have not yet been fully remediated. 

------------------------------------------------------------------------------
Does the Registrant use any cloud-based storage (e.g., Dropbox, SkyDrive, Google Docs, etc.) for data backup or any other purpose? If so, please list the vendors used and all due diligence research associate with each vendor.  Is the Registrant using a personal or business version of the cloud storage? Please provide a copy of the terms of service agreement from each cloud storage vendor that the Registrant is using.

------------------------------------------------------------------------------
Does the Registrant have any written policies and procedures to govern the use of/access of firm data? If so, please provide copies of the policies and procedures.

------------------------------------------------------------------------------
Has the Registrant every had any data breaches or any other cybersecurity issues (e.g., hacking incidents, ransomware, etc.)? If yes, please provide a timeline and describe the nature of the incident.  If no, please describe how you monitor for breaches.


------------------------------------------------------------------------------
If cybersecurity roles and responsibilities for the Firm’s workforce and managers have been explicitly assigned and communicated, please provide written documentation of these roles and responsibilities. If no written documentation exists, please provide a brief description. 

------------------------------------------------------------------------------
Please provide a copy of the Firm’s written business continuity of operations plan that addresses mitigation of the effects of a cybersecurity incident and/or recovery from such an incident if one exists. 


------------------------------------------------------------------------------
Does the Firm have a Chief Information Security Officer or equivalent position? If so, please identify the person and title. If not, where does principal responsibility for overseeing cybersecurity reside within the Firm?


------------------------------------------------------------------------------
Does the Firm maintain insurance that specifically covers losses and expenses attributable to cybersecurity incidents? If so, please briefly describe the nature of the coverage and indicate whether the Firm has filed any

claims, as well as the nature of the resolution of those claims. 

------------------------------------------------------------------------------
Does the Registrant allow employees (or any person) to access any personal web-based e-mail accounts (e.g., Google, Yahoo Mail, Hotmail, etc.) from the firm’s networks? If no, what steps has the Registrant taken to block network access to personal e-mail?

------------------------------------------------------------------------------
Does the Registrant allow employees (or any person) to use their personal e-mail for business purposes? If yes, what types of information are transmitted via web-based e-mail? Is web-based e-mail used for client communications?

------------------------------------------------------------------------------
Does the Registrant use a web-based e-mail provider’s or its own server for e-mail? If the Registrant is using a web-based e-mail account does it have a business account with the provider?  Do any other entities share the same email server?


------------------------------------------------------------------------------
Please provide a copy of the terms of service agreement from each web-based e-mail provider that the Registrant is using.


------------------------------------------------------------------------------
Does the Registrant maintain records of web-based e-mail communications? If so, how are the records maintained? Does compliance review web-based e-mail communications?


------------------------------------------------------------------------------
Does the Registrant have any written policies and procedures to govern the access to/use of/maintenance of/review of web-based e-mail? If yes, please provide copies of the policies and procedures.


------------------------------------------------------------------------------
Please identify any published cybersecurity risk management process standards, such as those issued by the National Institute of Standards and Technology (NIST) or the International Organization for Standardization (ISO), the Firm has used to model its information security architecture and processes. 


------------------------------------------------------------------------------
Please indicate which of the following practices and controls regarding the protection of its networks and information are utilized by the Firm, and provide any relevant policies and procedures for each item. 
  1. The Firm provides written guidance and periodic training to employees concerning information security risks and responsibilities. If the Firm provides such guidance and/or training, please provide a copy of any related written materials (e.g., presentations) and identify the dates, topics, and which groups of employees participated in each training event conducted since January 1, 2013. 
  2. The Firm maintains controls to prevent unauthorized escalation of user privileges and lateral movement among network resources. If so, please describe the controls, unless fully described within policies and procedures. 
  3. The Firm restricts users to those network resources necessary for their business functions. If so, please describe those controls, unless fully described within policies and procedures. 
  4. The Firm maintains an environment for testing and development of software and applications that is separate from its business environment. 
  5.  The Firm maintains a baseline configuration of hardware and software, and users are prevented from altering that environment without authorization and an assessment of security implications. 
  6. The Firm has a process to manage IT assets through removal, transfers, and disposition. 
  7. The Firm has a process for ensuring regular system maintenance, including timely installation of software patches that address security vulnerabilities. 
  8. The Firm’s information security policy and training address removable and mobile media.
  9.  The Firm maintains controls to secure removable and portable media against malware and data leakage. If so, please briefly describe these controls. 
  10. The Firm maintains protection against Distributed Denial of Service (DDoS) attacks for critical internet-facing IP addresses. If so, please describe the internet functions protected and who provides this protection. 
  11. The Firm maintains a written data destruction policy. 
  12. The Firm maintains a written cybersecurity incident response policy. If so, please provide a copy of the policy and indicate the year in which it was most recently updated. Please also indicate whether the Firm conducts tests or exercises to assess its incident response policy, and if so, when and by whom the last such test or assessment was conducted. 
  13. The Firm periodically tests the functionality of its backup system. If so, please provide the month and year in which the backup system was most recently tested.

------------------------------------------------------------------------------
Please indicate whether the Firm makes use of encryption. If so, what categories of data, communications, and devices are encrypted and under what circumstances? 

------------------------------------------------------------------------------
Please indicate whether the Firm conducts periodic audits of compliance with its information security policies. If so, in what month and year was the most recent such audit completed, and by whom was it conducted? 

------------------------------------------------------------------------------
Please indicate whether the Firm provides customers with on-line account access. If so, please provide the following information:
a. The name of any third party or parties that manage the service.
b. The functionality for customers on the platform (e.g., balance inquiries, address and contact information changes, beneficiary changes, transfers among the customer’s accounts, withdrawals or other external transfers of funds). c. How customers are authenticated for on-line account access and transactions.
d. Any software or other practice employed for detecting anomalous transaction requests that may be the result of compromised customer account access.
e. A description of any security measures used to protect customer PINs stored on the sites.
f. Any information given to customers about reducing cybersecurity risks in conducting transactions/business with the Firm. 


------------------------------------------------------------------------------
Please provide a copy of the Firm’s procedures for verifying the authenticity of email requests seeking to transfer customer funds. If no written procedures exist, please describe the process. 

------------------------------------------------------------------------------
Please provide a copy of any Firm policies for addressing responsibility for losses associated with attacks or intrusions impacting customers. a. Does the Firm offer its customers a security guarantee to protect them against hacking of their accounts? If so, please provide a copy of the guarantee if one exists and a brief description. 


------------------------------------------------------------------------------
If the Firm conducts or requires cybersecurity risk assessments of vendors and business partners with access to the Firm’s networks, customer data, or other sensitive information, or due to the cybersecurity risk of the outsourced function, please describe who conducts this assessment, when it is required, and how it is conducted. If a questionnaire is used, please provide a copy. If assessments by independent entities are required, please describe any standards established for such assessments.


------------------------------------------------------------------------------
If the Firm regularly incorporates requirements relating to cybersecurity risk into its contracts with vendors and business partners, please describe these requirements and the circumstances in which they are incorporated. Please provide a sample copy.


------------------------------------------------------------------------------
Please provide a copy of policies and procedures and any training materials related to information security procedures and responsibilities for trainings conducted since January 2017 for vendors and business partners authorized to access its network. 


------------------------------------------------------------------------------
If the Firm assesses the segregation of sensitive network resources from resources accessible to third parties, who (business group/title) performs this assessment, and provide a copy of any relevant policies and procedures? 


------------------------------------------------------------------------------
If vendors, business partners, or other third parties may conduct remote maintenance of the Firm’s networks and devices, describe any approval process, logging process, or controls to prevent unauthorized access, and provide a copy of any relevant policies and procedures. 


------------------------------------------------------------------------------
For each of the following practices employed by the Firm to assist in detecting unauthorized activity on its networks and devices, please briefly explain how and by whom (title, department and job function) the practice is carried out.
• Identifying and assigning specific responsibilities, by job function, for detecting and reporting suspected unauthorized activity.
• Maintaining baseline information about expected events on the Firm’s network.
• Aggregating and correlating event data from multiple sources.
• Establishing written incident alert thresholds.
• Monitoring the Firm’s network environment to detect potential cybersecurity events.
• Monitoring the Firm’s physical environment to detect potential cybersecurity events.
• Using software to detect malicious code on Firm networks and mobile devices.
• Monitoring the activity of third party service providers with access to the Firm’s networks.
• Monitoring for the presence of unauthorized users, devices, connections, and software on the Firm’s networks.
• Evaluating remotely-initiated requests for transfers of customer assets to identify anomalous and potentially fraudulent requests.
• Using data loss prevention software.
• Conducting penetration tests and vulnerability scans. If so, please identify the month and year of the most recent penetration test and recent vulnerability scan, whether they were conducted by Firm employees or third parties, and describe any findings from the most recent risk test and/or assessment that were deemed to be potentially moderate or high risk but have not yet been addressed.
• Testing the reliability of event detection processes. If so, please identify the month and year of the most recent test.
• Using the analysis of events to improve the Firm’s defensive measures and policies.


------------------------------------------------------------------------------
Did the Firm update its written supervisory procedures to reflect the Identity Theft Red Flags Rules, which became effective in 2013 (17 CFR § 248—Subpart C—Regulation S-ID)?
a. If not, why? 


------------------------------------------------------------------------------
How does the Firm identify relevant best practices regarding cybersecurity for its business model? 

------------------------------------------------------------------------------
Since January 1, 2016, has your Firm experienced any of the following types of events? If so, please provide a brief summary for each category listed below, identifying the number of such incidents (approximations are acceptable when precise numbers are not readily available) and describing their significance and any effects on the Firm, its customers, and its vendors or affiliates. If the response to any one item includes more than 10 incidents, the respondent may note the number of incidents and describe incidents that resulted in losses of more than $5,000, the unauthorized access to customer information, or the unavailability of a Firm service for more than 10 minutes. The record or description should, at a minimum, include: the extent to which losses were incurred, customer information accessed, and Firm services impacted; the date of the incident; the date the incident was discovered and the remediation for such incident.
• Malware was detected on one or more Firm devices. Please identify or describe the malware.
• Access to a Firm web site or network resource was blocked or impaired by a denial of service attack. Please identify the service affected, and the nature and length of the impairment.
• The availability of a critical Firm web or network resource was impaired by a software or hardware malfunction. Please identify the service affected, the nature and length of the impairment, and the cause.
• The Firm’s network was breached by an unauthorized user. Please describe the nature, duration, and consequences of the breach, how the Firm learned of it, and how it was remediated.
• The compromise of a customer’s or vendor’s computer used to remotely access the Firm’s network resulted in fraudulent activity, such as efforts to fraudulently transfer funds from a customer account or the submission of fraudulent payment requests purportedly on behalf of a vendor.
• The Firm received fraudulent emails, purportedly from customers, seeking to direct transfers of customer funds or securities.
• The Firm was the subject of an extortion attempt by an individual or group threatening to impair access to or damage the Firm’s data, devices, network, or web services.
• An employee or other authorized user of the Firm’s network engaged in misconduct resulting in the misappropriation of funds, securities, sensitive customer or Firm information, or damage to the Firm’s network or data.

 
------------------------------------------------------------------------------
Since January 1, 2016, if not otherwise reported above, did the Firm, either directly or as a result of an incident involving a vendor, experience the theft, loss, unauthorized exposure, or unauthorized use of or access to customer information? Please respond affirmatively even if such an incident resulted from an accident or negligence, rather than deliberate wrongdoing. If so, please provide a brief summary of each incident or a record describing each incident. Please indicate whether it was reported to the following:
• Law enforcement (please identify the entity)
• FinCEN (through the filing of a Suspicious Activity Report)
• FINRA • A state or federal regulatory agency (please identity the agency and explain the manner of reporting)
• An industry or public-private organization facilitating the exchange of information about cybersecurity incidents and risks 

------------------------------------------------------------------------------
What does the Firm presently consider to be its three most serious cybersecurity risks, and why? 


------------------------------------------------------------------------------
Please feel free to provide any other information you believe would be helpful to the Securities and Exchange Commission in evaluating the cybersecurity posture of the Firm or the securities industry.  




Share

0 Comments

7/16/2019

Simple Cybersecurity Technical Controls for RIAs, IBDs, and Hedge Funds

0 Comments

Read Now
 

Cybersecurity Technical Controls for RIAs, IBDs, and Hedge Funds

Are you a new CCO looking to get your head around your cybersecurity framework or a seasoned pro looking for a checklist?

Either way, these 12 steps help you strengthen your cybersecurity defenses.

To be clear: These are not a "nice to have" or "a cool feature". This stuff is mandatory for ALL firms.
​
  1. Install and maintain firewalls to protect data
  2. Change default passwords on all firm  devices and systems (ESPECIALLY your router and modem)
  3. Encrypt all hard drives.
  4. Encrypt transmission of client data.
  5. Use Antivirus and Antimalware software on all firm devices. Use VPN services for all mobile devices.
  6. Use only software and systems that allow for 2-factor authentication. Physical keys like Yubiko or Thetis are preferred.
  7. Restrict access to sensitive data. Only those with a need get access.
  8. Assign unique usernames to all employees who access your client's data. No sharing of passwords. Ever.
  9. Restrict physical access to the data. Lock your office, enable mobile wipe, GPS tracking, etc.
  10. Monitor and log all access to data and network resources.
  11. Perform vulnerability scans and penetration tests on your network at least annually.
  12. Document Everything! If you don't properly document it, it didn't happen.

​

Share

0 Comments

7/16/2019

SEC and FINRA CCOs: How to conduct vendor cybersecurity due-diligence reviews.

0 Comments

Read Now
 

SEC and FINRA CCOs: How to conduct vendor cybersecurity due-diligence reviews.

It is a chore. I get it. But, as CCO, you are required to be performing cybersecurity due diligence audits on all third-party vendors that "touch" your client's personally identifiable information (PII).

Here is a quick guide to help you streamline this process.

Understand what data you will be providing to the vendor.
Not all vendors have the same access. Determine the sensitive nature of the data, the source of the data, and which internal systems the vendor will have access to.

Understand which products and services you are interested in (or using)
A vendor may offer both hosted services and on-premise software. Each service provider and service offering will have a different set of questions that need to be asked. If you let the vendor know which services you are using or interested in the vendors can provide the most relevant information. If you ask for an assessment applicable to all their products and services you’re much less likely to get a usable response.

Craft the questions to the specific risks associated with that particular vendor:
The vendor may already have documentation readily available that covers your concerns (and many more) so be sure to ask for that. If they have a been through a third party cybersecurity audit, you can ask for those results (Heads Up : The vendor will usually require an NDA before providing you with the reports.)

If adequate documentation is not available, here are some customizable vendor security questionnaires you can start with to craft your own:
  • Consensus Assessments Initiative Questionnaire (CAIQ) offered by the Cloud Security Alliance
  • Standardized Information Gathering (SIG) questionnaire sold by Shared Assessments
  • Vendor Security Alliance questionnaire


When choosing which questions to include in your outreach, consider the following:
  • Where will the vendor store your data?
  • How will the vendor encrypt your data? (In transit, in use, and at rest?)
  • How robust is the vendor’s ability to identify, respond to and notify you of a security incident affecting your data/systems? What protocols and systems are in place?
  • How long will the vendor retain the data? Do they meet SEC and FINRA compliance requirements?


If this vendor is a critical part of your business operations (trading platform, custodian, etc), you will also want to understand:
  • What steps does the vendor take to ensure resilience and business continuity in the event of external and internal disruptive events?


Ongoing Maintenance
I suggest that you reassess your due diligence assessment annually as part of your annual compliance review.
And, of course, if you don't document this process, it didn't happen.

Document everything.



​

Share

0 Comments

1/1/2019

12 Steps to Cybersecurity for RIAs, IBDs, and Hedge Funds

0 Comments

Read Now
 

Step 1:

Install and maintain a firewall to protect data.



Step 2:

Change default (vendor supplied) passwords on all firm devices and systems.



Step 3:

Encrypt all hard drives.



Step 4:

Encrypt transmission (internal or external) of client data.


Step 5:

Use AntiVirus and Malware detection software on all devices. Use VPN services for all mobile devices.



Step 6:

Use only systems that allow for 2-factor authentication (Yubiko key, Google Authenticator, etc).



Step 7:

Restrict access to data only to those who need it to function in their jobs.



Step 8:

Assign unique usernames to all employees who accesses your client's data. No sharing of passwords.



Step 9:

Restrict physical access to the data. Lock your office, enable mobile wipe, etc.



Step 10:

Monitor and log all access to data and network resources.



Step 11:

Perform Vulnerability scans on systems quarterly.



Step 12:

​Document EVERYTHING!

Share

0 Comments
Details

    RSS Feed


Picture
  • Home
  • SEC and FINRA Services
  • Chief Hacking Officer
  • Red Team
  • Penetration Testing
  • Threatwire Articles
    • The SEC OCIE Cybersecurity Observations Decoded
    • The SEC and Cybersecurity Documentation
    • The Dark Web and Advisory Firms
    • DIY Guide to SEC and FINRA Cybersecurity Vulnerability Scanning
    • The Biggest Cybersecurity Mistake
    • Hackers and Remote Workers
    • A Criminal's Retirement Plan
    • Home Security System Hacking
    • IT Asset Inventory
  • Schedule a Meeting