We changed our name from IT Central Station: Here's why

Top 8 IoT Security Tools

Forescout PlatformBarracuda CloudGen FirewallArmisNozomi NetworksMcAfee Embedded ControlLynxSecure Separation Kernel HypervisorMocanaDxOdyssey
  1. leader badge
    The most valuable feature of the Forescout Platform is the large capacity it can handle. Additionally, the interface of the platform is good.Within three or four days, we have complete visibility of your infrastructure on the network. Compared to other solutions, the deployment of the solution is easier and we can close the project quickly.
  2. Its central management, especially when it comes to distributed environments, is great. I can generate and save a setting and then apply that setting across the network with just one click.
  3. Find out what your peers are saying about Barracuda CloudGen Firewall vs. Forescout Platform and other solutions. Updated: January 2022.
    564,599 professionals have used our research since 2012.
  4. report
    Use our free recommendation engine to learn which IoT Security solutions are best for your needs.
    564,599 professionals have used our research since 2012.

Advice From The Community

Read answers to top IoT Security questions. 564,599 professionals have gotten help from our community of experts.
Evgeny Belenky
Hi peers, I believe many of you have already heard of the recent Log4j/Log4Shell vulnerability that allows attackers to perform remote code execution (RCE). What does it mean for an organization? How can you check you're vulnerable and mitigate/patch it now, if at all? Lastly, what impact do you see this can have in the near future? Thanks
author avatarSimonClark
Reseller

This vulnerability is particularly critical because Log4j is widely used in open source and commercial software and remote exploitation of the vulnerability against any internet-facing server is trivial using a single HTTP post. Exploitation results in full system compromise. The vulnerability has a CVSS Score of 10 out of a possible 10 meaning it is as bad as it gets.


Our SOC has launched a new app that detects the presence of vulnerable versions of Log4j however, detecting it does not mean you have been exploited.


My advice: Scan your network to get a full visibility report i.e. find all your legacy and shadow IT that you didn't know existed which means you should find all potential instances of Log4j, patch all of the Log4J environments, monitor your systems 24/7 using your SOC and if you don't have a SOC invest in a Managed SOC provider. 

author avatarITSecuri7cfd (IT Security Coordinator at a healthcare company with 10,001+ employees)
Real User

Yet another chance to test our incident response procedures. 


So far I would say we're a B. Good on the process, and an A on team response and interactions and reducing threat risk were about a B. 


ID'g your external assets exposed to this vulnerability is your teams' #1 priority and mitigate or patch (if available) the threat. 


You also have to notify and communicate with any 3rd party to make sure they're aware so they can start the same process. You ALSO need to be fully aware of your vendors' weaknesses and defenses (mitigations, patches, knowledge and reaction time). 


Then be prepared to roll out patches or in this case shut systems down OR put mitigations in place immediately to mitigate risk to the entire environment.

author avatarJairo Willian Pereira
Real User

One excellent opportunity for the company to test your CMDB/Inventory (at medium and big companies). 


Tenable, and I think, other Vulnerability Scanners offer a specific plugin used to check your infrastructure against Log4shell. 


If you don't have VS, you can try looking at your logging system for evidence or use:


https://buff.ly/3lYZRh0
https://gist.github.com/SwitHa...


In the future, Patch Mgmt pre-defined and applied schedules need to be first (proactive) from scanners/vulns. (reactive).

author avatarreviewer1572348 (Chief Architect at a computer software company with 10,001+ employees)
Real User

WhiteSource has released a utility to detect log4j vulnerability in the codebase. 


Take a look at this if it helps. In our case, a lot of projects use Elastic Search and Azure DevOps Server - both of them have log4j being used and that's where additional fixes have to be done.


https://github.com/whitesource/log4j-detect-distribution


IoT Security Articles

Evgeny Belenky
PeerSpot (formerly IT Central Station)
Nov 19 2021
Hi community members, Spotlight #2 is our fresh bi-weekly community digest for you. It covers cybersecurity, IT and DevOps topics. Check it out and comment below with your feedback! Trending What are the pros and cons of internal SOC vs SOC-as-a-Service? Join The Moderator Team at IT Ce...
Read More »
Find out what your peers are saying about Barracuda CloudGen Firewall vs. Forescout Platform and other solutions. Updated: January 2022.
564,599 professionals have used our research since 2012.