Home

Azure Security Center previews new threat detections for Linux

%3CLINGO-SUB%20id%3D%22lingo-sub-122919%22%20slang%3D%22en-US%22%3EAzure%20Security%20Center%20previews%20new%20threat%20detections%20for%20Linux%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-122919%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20Security%20Center%20recently%20launched%20a%20limited%20preview%20of%20new%20analytics%20that%20leverage%20auditd%20records%20to%20detect%20malicious%20behaviors%20on%20cloud%20and%20on-premises%20Linux%20machines.%20Similar%20to%20Security%20Center%20detections%20for%20Windows%20machines%2C%20these%20new%20capabilities%20can%20be%20used%20to%20detect%20suspicious%20processes%2C%20dubious%20login%20attempts%2C%20kernel%20module%20loading%2Funloading%2C%20and%20other%20activities%20that%20could%20indicate%20that%20a%20machine%20is%20under%20attack%20or%20have%20been%20breached.%20These%20are%20in%20addition%20to%20network%20detections%20that%20were%20previously%20available%20for%20Linux%2C%20as%20well%20as%20Windows%2C%20VMs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESecurity%20Center%20collects%20audit%20records%20from%20Linux%20machines%20using%20auditd%2C%20one%20of%20the%20most%20common%20Linux%20auditing%20frameworks.%20Auditd%20has%20the%20advantage%20of%20having%20been%20around%20for%20a%20long%20time%20and%20living%20in%20the%20mainline%20kernel.%20The%20auditd%20system%20consists%20of%20two%20major%20components.%20The%20first%20is%20a%20set%20of%20user-space%20utilities%20offering%20a%20wide%20collection%20of%20operations%20allowing%20administrators%20to%20better%20adjust%20rules%2C%20analyze%20audit%20log%20files%20or%20troubleshoot%20if%20things%20are%20misconfigured.%20The%20second%20is%20a%20kernel-level%20subsystem%20which%20is%20responsible%20for%20monitoring%20system%20calls%2C%20filtering%20them%20by%20given%20rule%20set%2C%20and%20writing%20match%20messages%20to%20a%20buffer.%20Both%20components%20are%20communicating%20through%20a%20netlink%20socket.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F23271iBA3234F1FA0A7D72%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Slide1.PNG%22%20title%3D%22Slide1.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERead%20about%20it%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fazure-security-center-previews-new-threat-detections-for-linux%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20blog%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-122919%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESecurity%20Center%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Community Manager

Azure Security Center recently launched a limited preview of new analytics that leverage auditd records to detect malicious behaviors on cloud and on-premises Linux machines. Similar to Security Center detections for Windows machines, these new capabilities can be used to detect suspicious processes, dubious login attempts, kernel module loading/unloading, and other activities that could indicate that a machine is under attack or have been breached. These are in addition to network detections that were previously available for Linux, as well as Windows, VMs.

 

Security Center collects audit records from Linux machines using auditd, one of the most common Linux auditing frameworks. Auditd has the advantage of having been around for a long time and living in the mainline kernel. The auditd system consists of two major components. The first is a set of user-space utilities offering a wide collection of operations allowing administrators to better adjust rules, analyze audit log files or troubleshoot if things are misconfigured. The second is a kernel-level subsystem which is responsible for monitoring system calls, filtering them by given rule set, and writing match messages to a buffer. Both components are communicating through a netlink socket.

 

Slide1.PNG

 

Read about it in the Azure blog.