Showing posts with label cyber. Show all posts
Showing posts with label cyber. Show all posts

Sunday, April 30, 2023

Getting to "Zero Trust" architecture and philosophy


In PMO school, they teach you that trust is everything when building a successful project team.
Fair enough.

But now comes "Zero Trust", and the "Zero Trust Architecture" which is more like a philosophy than an architecture. And, of course, the acronyms: ZT and ZTA.

I don't know if NIST (*) coined this phrase, 'zero trust', but they have a proposed zero trust architecture you can read about here. 

Motive
The motive for developing ZTA was a realization that security threats to an enterprise's intellectual property (IP), whether corporate proprietary or government classified, are more often now inside the perimeter of a security firewall. Indeed, with the proliferation of remote working, the 'cloud, and 'bring-your-own-device (BYOD), the very idea of a perimeter is somewhat bye-the-bye. And so IP protection can no longer just be a matter of a security firewall around the enterprise.

Philosophy
So if you are philosophically in touch with 'zero trust', the idea is that every element of IP is subject to an enforced need-to-know, and an enforced limitation on copy and dissemination. The perimeter really no longer exists; a pass through the perimeter, even if existent, is relatively unproductive because of ZT gates on the IP.

The idea is to move from protecting a perimeter or a network segment to protecting the actual resource that is the IP of the enterprise. In effect, it is realized that there will be persistent active threats in the network; the security objective is to block them from accessing the actual IP.

ZT according to NIST
NIST says this: "Zero trust (ZT) is the term for an evolving set of cybersecurity paradigms that move defenses from static, network- based perimeters to focus on users, assets, and resources. A zero trust architecture (ZTA) uses zero trust principles to plan industrial and enterprise infrastructure and workflows.

ZT is not a single architecture but a set of guiding principles for workflow, system design and operations that can be used to improve the security posture of any classification or sensitivity level. Zero trust (ZT) provides a collection of concepts and ideas designed to minimize uncertainty in enforcing accurate, least privilege per-request access decisions in information systems and services in the face of a network viewed as compromised.  

Zero trust assumes there is no implicit trust granted to assets or user accounts based solely on their physical or network location (i.e., local area networks versus the internet) or based on asset ownership (enterprise or personally owned). Authentication and authorization (both subject and device) are discrete functions performed before a session to an enterprise resource is established. 

Zero trust is a response to enterprise network trends that include remote users, bring your own device (BYOD), and cloud- based assets that are not located within an enterprise-owned network boundary. Zero trust focus on protecting resources (assets, services, workflows, network accounts, etc.), not network segments, as the network location is no longer seen as the prime component to the security posture of the resource."

NIST continues: 
"In this new paradigm, an enterprise must assume no implicit trust and continually analyze and evaluate the risks to its assets and business functions and then enact protections to mitigate these risks. In zero trust, these protections usually involve minimizing access to resources (such as data and compute resources and applications/services) to only those subjects and assets identified as needing access as well as continually authenticating and authorizing the identity and security posture of each access request."

Their conclusion:
"When balanced with existing cybersecurity policies and guidance, identity and access management, continuous monitoring, and best practices, a ZTA can protect against common threats and improve an organization’s security posture by using a managed risk approach.

_______________
(*) NIST: National Institute for Standards and Technology
 


Like this blog? You'll like my books also! Buy them at any online book retailer!

Monday, May 4, 2015

Protecting the integrity of software


Breakdowns, security, hazards, etc are all over the place these days, and so Matthew Squair's presentation on Software Partitioning Integrity is very timely. He subtitles it "A short tutorial on the basic architectural principles of integrity level partitioning"

You'll learn pithy things like this:
If You Can Keep Them Separate (Partitioning)
Then You Can Bring Them Together (Composition)
Greve & Wilding HCSS 03
Of course in the world of system engineering, we talk about decoupling and coupling, the former to manage the propagation of risk and provide for independence of action; the latter to create a means for integrating actions.

And, at an even higher level, these principles are applicable to portfolios, and the way projects, scope, and security is partitioned among portfolio constituents.

A few definitions are helpful, especially when looking at the system either in terms of safety or security (perhaps attention to aircraft cockpit security could benefit by this):
Strict Protection
– Component X can be said to be strictly protected from Y if any behavior of
Y has no effect on the operation of X
Safety Protection
– Component X can be said to be safely protected from Y if any behavior of
Y has no effect on the safety properties of X
 Two-way (symmetric) protection
– Component X is protected from Y, and Y is protected from X
 One-way (asymmetric) protection
– Component X is protected from Y, but component Y is not protected from
X
Beyond software
This presentation actually goes beyond software to the very top of the architecture, to include hardware, and the interactions of hardware and software vis a vis safety, isolation, and protection.

If you're in this business (and actually who is not thinking of security these days) this is a good read.

Read in the library at Square Peg Consulting about these books I've written
Buy them at any online book retailer!
http://www.sqpegconsulting.com
Read my contribution to the Flashblog

Friday, July 19, 2013

Mobile device security


What project is not running these days with some number of mobile devices? In fact, the question may be put the other way around -- what projects are running with laptops or desktops? Likely the answer to this is "all of the above"

With that in mind, you might be interested in this blurb from the NIST:

The National Institute of Standards and Technology (NIST) has published a mobile device management guide...
Employees want to be connected to work through mobile devices for flexibility and efficiency, and managers can appreciate that. However, the technology that delivers these advantages also provides challenges ... because these devices can be more vulnerable.
...
Guidelines for Managing the Security of Mobile Devices in the Enterprise helps ... organizations struggling with this dilemma.
The revised guidelines recommend using centralized device management at the organization level to secure both .. issued and individually owned devices used for ... business.
...
Other key recommendations include instituting a mobile device security policy, implementing and testing a prototype of the mobile device solution before putting it into production, securing each organization-issued mobile device before allowing a user to access it, and maintaining mobile device security.

Check out these books I've written in the library at Square Peg Consulting

Friday, April 26, 2013

NIST Cyber framework


Here's an FYI for those with projects in the cyber security domain:

The National Institute of Standards and Technology (NIST) is holding the second of four planned workshops to develop a voluntary framework to reduce cybersecurity risks for critical infrastructurefrom May 29-31, 2013, at Carnegie Mellon University in Pittsburgh, Pa. The hands-on workshop is open to cybersecurity industry experts in all sectors—such as energy, finance, transportation and communications—as well as government and academic stakeholders.

The second workshop on the Cybersecurity Framework will be an opportunity for attendees to identify, refine, and guide the many interrelated considerations, challenges, and efforts needed to develop the Framework. The majority of the workshop will be working sessions where participants will analyze and discuss the initial inputs to the Framework...




Check out these books I've written in the library at Square Peg Consulting