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
Playing It Straight: Building A Risk-Based Approach To InfoSec
Newest First  |  Oldest First  |  Threaded View
Uri Rivner
50%
50%
Uri Rivner,
User Rank: Author
12/9/2015 | 10:48:17 AM
Dynamic risk-based decisions
Great as always Josh.

Beyond making risk-based choices, it's time the enterprise begin to realise that the authentication and authorization paradigms that have been with us since the dawn of corporate security history are all but dead. What does an authentication session mean anyway these days? All fraud cases in online banking come from authenticated sessions. All hacks come from authenticated nodes.

The same applies to authorization. Take RBAC - a fundumental principal in security. Josh is a CTO, so he has access to this-and-that. Unless Josh changes his role, or unless that role needs an updated access scheme, that's basically it. But in today's reality, it's totally rubish. Yes, Josh is entitled to access this-and-that, but only if I think it's really Josh, and he really needs that access right now. If there are signs of foul play, I may change my mind. And if I have an ability to dynamically change my mind about authorization, and make sure people get access based on the risk for this specific activity, I'm far better off.

The same goes for my smart home app, the one I'm using to control my smart home. Once I authenticated, I have full access to everything. That's history. Future is different: far more agile and adaptive. The more it looks like me, and the lowest the risk with my current actions, the greater control I should have. And think of IOT appliances as well - they also have authentication and authorization controls that are totally black and white, and without giving it shades and adaptiveness - we'll be screwed a few years from now.

The enterprise security paradigms need some heavy shaking, become far more dynamic, adaptive and risk-based, so real time decisions can be made instantly for every activity.

 
gszathmari
50%
50%
gszathmari,
User Rank: Apprentice
12/7/2015 | 6:00:08 PM
Risk based approach is the king
The risk based approach is the only way that ensures money and time is spent on the right things for protecting the organisation. Risk can be managed on multiple levels, starting from the business risks, throughout IT and infosec risks all down to the code level.

I also wrote an article today on risk driven approach, but on incident management. This approach allows incident response teams to focus on the critical areas with their efforts. The post is available on Rainbow and Unicorn blog.


Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16632
PUBLISHED: 2021-05-15
A XSS Vulnerability in /uploads/dede/action_search.php in DedeCMS V5.7 SP2 allows an authenticated user to execute remote arbitrary code via the keyword parameter.
CVE-2021-32073
PUBLISHED: 2021-05-15
DedeCMS V5.7 SP2 contains a CSRF vulnerability that allows a remote attacker to send a malicious request to to the web manager allowing remote code execution.
CVE-2021-33033
PUBLISHED: 2021-05-14
The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
CVE-2021-33034
PUBLISHED: 2021-05-14
In the Linux kernel before 5.12.4, net/bluetooth/hci_event.c has a use-after-free when destroying an hci_chan, aka CID-5c4c8c954409. This leads to writing an arbitrary value.
CVE-2019-25044
PUBLISHED: 2021-05-14
The block subsystem in the Linux kernel before 5.2 has a use-after-free that can lead to arbitrary code execution in the kernel context and privilege escalation, aka CID-c3e2219216c9. This is related to blk_mq_free_rqs and blk_cleanup_queue.