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.

Risk

Guest Blog // Selected Security Content Provided By Intel
What's This?
12/13/2013
05:49 PM
Guest Blogs
Guest Blogs
Guest Blogs
50%
50%

Stronger Defense Against Malware Happens Below App Level

We need to build security solutions on strong foundations that ensure we can 'start secure' and 'run secure'

I think most of you'd agree that among the toughest challenges in fighting malware is sorting out what ought to run from what needs to be stopped. Your increasingly sophisticated adversaries hide, run 0-days, and design advanced attacks that evade common detection tools. Sadly, the adversaries will grow only more sophisticated. Future security solutions must do more to keep pace. And to successfully keep pace, we need to build security solutions on strong foundations that ensure we can "start secure" and "run secure."

"Starting secure" is crucial. At power-on and start-up phases, our system and infrastructure are at their most vulnerable because defensive systems have not been brought online to protect them. The industry has definitely made some progress here. For example, modern operating systems have helped ease deployment of secure boot capabilities -- effectively slamming shut the door on malware trying to penetrate and corrupt boot-time operations. For the highest level of protection, industry standards-based technology, such as that from Secure Boot or the Trusted Computing Group, is available today that measures each element of code executing through the boot sequence, and permits execution of that element only if it can be verified as legit. And the same capabilities that harden boot operations can be extended into new applications to help strengthen cloud security.

To improve the odds of "running secure," new capabilities in processors and popular operating can effectively increase your system's immunity to attack. New innovations build on baseline microprocessor architecture to restrict how, when, and where code can execute. For example, Intel and AMD introduced capabilities more than 10 years ago to stop code from executing in certain regions of memory reserved for data. Today, operating systems and new PC and server processors have greatly enhanced capabilities that can defeat some classes of malware associated with buffer overflow attacks. One recent enhancement from Intel comes in a capability called Intel® OS Guard, which prevents some types of privilege escalation attacks. So instead of relying solely on recognizing malware, the system itself becomes stronger and better able to resist malware.

To learn more about emerging systems and infrastructure that "run secure," look for combinations of hardware and operating systems that enable deeper system behavior monitoring at low levels of the computing stack. By taking advantage of processor technologies embedded in the silicon, the software provides something like close inspection and repair of plumbing or wiring in an apartment building, detecting and preventing malicious intent at the hardware level.

If you need the strongest possible foundation and support for your anti-malware regimen, then look below the application layer to assess what new OS and hardware capabilities can do to enhance your defenses.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
macker490
50%
50%
macker490,
User Rank: Ninja
1/14/2014 | 1:02:32 PM
re: Stronger Defense Against Malware Happens Below App Level
there are two principle rules for secure computers:
1. the O/S must not permit itself to be modified by an application program. updates must be via an authorized update system only.
2. the system owner or operator must be able to regulate what an application program is allowed to access or update.

(1) depends on the computer chip offering protected mode operation. This became standard on IBM System/360 in 1964, and to x86 with 80386 in 1985. PGP became available in 1992.
(2) depends on security software running in portected mode checking and granting access to system resources based on owner/operator specifications. RACF was added to System/360/370 in 1974. Apparmor appeared in 1998.

the first step in recovering the security debauch is in general education. people should know the general mess we have on our hands now -- is not necessary.
macker490
50%
50%
macker490,
User Rank: Ninja
12/17/2013 | 12:21:52 PM
re: Stronger Defense Against Malware Happens Below App Level
as usual, a very insightful and excellent essay!!

==>"And to successfully keep pace, we need to build security solutions on
strong foundations that ensure we can "start secure" and "run secure." "

what this means: we do not run un-authorized programming. not in an application. not in the o/s.

modern documents must be treated as executable files. as a result it will be necessary to control what a user can do when using a particular program. for example, you would not want your web browser to open and access a PeopleSoft directory -- even though you -- as the workstation operator -- have access to that resource.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Vulnerability Disclosure Programs See Signups & Payouts Surge
Kelly Sheridan, Staff Editor, Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15216
PUBLISHED: 2020-09-29
In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. A patch is available, all users of goxmldsig should upgrade to at least revisio...
CVE-2020-4607
PUBLISHED: 2020-09-29
IBM Security Secret Server (IBM Security Verify Privilege Vault Remote 1.2 ) could allow a local user to bypass security restrictions due to improper input validation. IBM X-Force ID: 184884.
CVE-2020-24565
PUBLISHED: 2020-09-29
An out-of-bounds read information disclosure vulnerabilities in Trend Micro Apex One may allow a local attacker to disclose sensitive information to an unprivileged account on vulnerable installations of the product. An attacker must first obtain the ability to execute low-privileged code on the ...
CVE-2020-25770
PUBLISHED: 2020-09-29
An out-of-bounds read information disclosure vulnerabilities in Trend Micro Apex One may allow a local attacker to disclose sensitive information to an unprivileged account on vulnerable installations of the product. An attacker must first obtain the ability to execute low-privileged code on the ...
CVE-2020-25771
PUBLISHED: 2020-09-29
An out-of-bounds read information disclosure vulnerabilities in Trend Micro Apex One may allow a local attacker to disclose sensitive information to an unprivileged account on vulnerable installations of the product. An attacker must first obtain the ability to execute low-privileged code on the ...