Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Security & the Infinite Capacity to Rationalize
Newest First  |  Oldest First  |  Threaded View
DHorse2
50%
50%
DHorse2,
User Rank: Strategist
8/7/2019 | 8:32:12 PM
Rationalization is lazy?
No, it isn't. If you are going to solve this issue the first requirement is to understand it. And... well... that's a lazy, overly simplistic view as well as incorrect. Human thought reflects our nature as rapid response probabilistic state prediction biologicals. That was a lot of words. However note that neither logic nor laziness was in there. Logic is something applied selectively, judiciously and sparingly. Now, while agree that laziness is the mother of invention, thoughts are fleshed out emotions just as emotions are primitive thoughts. Your choice is made early and emotionally. Rationalization is how you justify it variously. That my friends is hard work!
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/6/2019 | 3:47:04 PM
Wonderful commentary

I agree with the statements made, we need to look at security from a logic standpoint where we start looking at the attacks from a mathematical perspective. For example, most of the files that come across are associated with a hash and the locations on the filesystem are related to inodes and hashes. We need to start looking at the file as a number, baseline all the numbers on the filesystem. The files can be identified by the changes associated with specific system files (pgp, kernel, binaries), that information is then gathered by creating an index; from the index we should be able to identify the changes in files, directories and file-types based on the number associated with that specific file (MD5 or SHA256). There is only a finite number of files that are essential to the system's function, once we isolate the files, then we can start to create an algorithm to index files based on purpose and location (SELinux does something very similar - files, directories, filesystem, policies, characteristics).

This will help with the machine learning and identification process because we will be able to identify the change(s) easier than using existing methods.




Some companies are doing this (pattern matching), we just need to do this type of analyis at the atomic level (using inodes and hashes), by developing equations to identify changes based on patterns or relationships, we can create ML structures that look at the system as an algorithic pattern (data flows).


Just a thought.


T


COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
'BootHole' Vulnerability Exposes Secure Boot Devices to Attack
Kelly Sheridan, Staff Editor, Dark Reading,  7/29/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16192
PUBLISHED: 2020-08-05
LimeSurvey 4.3.2 allows reflected XSS because application/controllers/LSBaseController.php lacks code to validate parameters.
CVE-2020-17364
PUBLISHED: 2020-08-05
USVN (aka User-friendly SVN) before 1.0.9 allows XSS via SVN logs.
CVE-2020-4481
PUBLISHED: 2020-08-05
IBM UrbanCode Deploy (UCD) 6.2.7.3, 6.2.7.4, 7.0.3.0, and 7.0.4.0 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 181848.
CVE-2020-5608
PUBLISHED: 2020-08-05
CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01 allows a remote unauthenticated attacker to bypass authentication and send altered c...
CVE-2020-5609
PUBLISHED: 2020-08-05
Directory traversal vulnerability in CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01 allows a remote unauthenticated attacker to cre...