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.


12:00 PM

Inside-Out Security

Basic defenses that lack depth create needless vulnerabilities - internal and external

8:00 AM -- Defense in depth -- it's a term we hear all the time in security, and some of us practice it without even realizing it. But it's probably one of the most important theories to a solid security architecture.

Let's look for a moment at what a normal, small, mom-and-pop e-commerce site looks like. It is probably running on Linux in a shared hosting environment, with FTP access. There's probably a firewall in place, but it allows inbound FTP, HTTP, and HTTPS from anywhere. It's unlikely that mom or pop even know how to link to the SSL-enabled portion of their site. The site allows PHP, PERL, and Java. The site does a fairly good job at isolating the user accounts in their respective FTP directories, but that's about all it does.

What I've described is vulnerable not just from the outside, but it's also vulnerable to man-in-the-middle attacks, as well as other users of the same system. It makes the assumption that the only people who are going to attack it are outside the perimeter, and there are no vulnerabilities in the Web application or the services provided. Furthermore, it makes an assumption about the fact that those protocols have nothing sensitive traveling over them.

This is about as simple as a network gets, and it's also just about as vulnerable as it gets. This is not a well defended application. While you are designing an application, you need to think about it from a number of attackers' perspectives -- remote attackers and insiders.

Insiders can be part of the company, or like in the case above, they can be other users of the same virtual system. Building up the network to defend against external threats makes sense, but you cannot rely on it alone, as you still need the application to listen on ports 80 and 443.

Understanding that should help explain why auditing code, and looking at the Web application as its own problem requiring additional layers of security, is critical to analyzing your risk profile. Adding layers is never a bad thing, as long as you aren't causing those layers to deny service when it is a critical, always-on type environment. Weigh your business risks against the Web application's purpose, as well as how it interacts with the rest of the system, its developers, and the consumer. And, oh yeah -- just say no to shared hosting if security is a concern.

— RSnake is a red-blooded lumberjack whose rants can also be found at Ha.ckers and F*the.net. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-12-07
The serialize-to-js NPM package before version 3.0.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.to...
PUBLISHED: 2019-12-06
In various functions of RecentLocationApps.java, DevicePolicyManagerService.java, and RecognitionService.java, there is an incorrect warning indicating an app accessed the user's location. This could dissolve the trust in the platform's permission system, with no additional execution privileges need...
PUBLISHED: 2019-12-06
In checkOperation of AppOpsService.java, there is a possible bypass of user interaction requirements due to mishandling application suspend. This could lead to local information disclosure no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVers...
PUBLISHED: 2019-12-06
In hasActivityInVisibleTask of WindowProcessController.java there?s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction ...
PUBLISHED: 2019-12-06
n ihevcd_parse_slice_data of ihevcd_parse_slice.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android...