For most, the question of - if they have caught all possible instances of Log4j is really the biggest question. The Log4j vulnerabilities were not something you could resolve with a simple update. It is a messaging component built into a variety of web services and vendor applications. It was difficult to detect in many cases, so code scanners and network vulnerability scanners struggled to accurately identify exposure. Organizations that were able to respond quickly found that truly understanding their exposure required rolling up their sleeves. They quickly assessed their internal development teams for use of Log4j and their vendor risk management process to determine what vendors they were consuming solutions from and assessing each to determine if they were exposed. As an additional step, security teams also utilized a variety of custom scanners purpose-built to scan for the Log4j binaries. This is crucial given Log4j was buried in many cases in a few layers of JAR files which was throwing many vulnerability scanners off. The vulnerability caused a new plague, impacting almost half of all companies worldwide in a very short space of time. Attackers are able to exploit vulnerable apps to execute cryptojackers and other malware on compromised servers. Until now, most of the attacks have focused on the use of cryptocurrency mining at the expense of the victims. However, advanced attackers have started to act aggressively and take advantage of the breach on high-quality targets. Microsoft Exchange administrators got a new year’s surprise as on-premises Exchange servers started experiencing email becoming stuck as queues ran into a date format issue in the Filtering Management Service. Guidance quickly became available on January 1, 2022, as email stuck in transport queues quickly got backed up

A report says, about 66% of organizations in India have suffered at least one data breach since shifting to a remote working model. With the global pandemic acting as.