Hey infosec peeps, it's been a weekend full of enterprise change management and still learning how to do proper remote administration. Now would be a great time to:
* Scan external ranges for RDP open to the Internet, if found ensure it is configured with NLA 1/
* Scan external ranges for RDP open to the Internet, if found ensure it is configured with NLA 1/
* Review DNS logs for evidence of remote access products installed internally. These include: TeamViewer, GotoMyPC, LogMeIn, etc.
* Examine netflow for abnormally long connections that shouldn't be there, e.g. illicit outbound VPNs used as a reverse tunnel for access. 2/
* Examine netflow for abnormally long connections that shouldn't be there, e.g. illicit outbound VPNs used as a reverse tunnel for access. 2/
* Audit your administrative groups for new members since the WFH migration began. A lot of organizations delegated new permissions on the fly to get people taken care of. Are these still needed?
* In addition to RDP exposed to the Internet, what other ports are there? SSH? 3/
* In addition to RDP exposed to the Internet, what other ports are there? SSH? 3/
* Finally, and this is a big one: review your firewall rules for changes in the last 30 days. Most organizations made some changes to support remote work in the moment that sacrificed confidentiality for availability. Hunt those down and start securing them if possible. /FIN
This is obviously not an exhaustive list, but it's where I'd start looking for low hanging fruit in an environment right now (and low hanging fruit is also what most attackers are looking for).
