Comments (5)
Interesting one. Here's my thoughts:
Derived PIV is a credential.
STS is an assertion (ephemeral token) mechanism.
to your point: STS could be referenced in an operational example, under one of the Access use cases?
from ficam-arch.
Access may make some sense. But, the conversations I heard seem to assume (read require) an LOA 4 credential. My concern is some individuals may NOT have the ability to present an LOA 4 credential.
If an organizational entity establishes a trusted STS and asserts the individual's identity, can this be done such that the identity is trusted at the LOA 4 level?
A target scenario is where the individual needs access to a resource (e.g., TSP account?), does not have a PIV but yet can access the resource via the organizations STS. The access should treat this as an LOA 4 access .....
from ficam-arch.
In LOA math, there is no concept for adding two separate identities (in this case a user and an STS) to increase the LOA. LOAs are defined in 800-63-2 as a low watermark approach - the strength is only as strong as its weakest link, for that user. Derived PIV, in my opinion, has done a lot of hand waving to explain why they are still LOA4, in all cases. This includes a USB or SIM card that can be easily separated from the device.
from ficam-arch.
This set of comments is still valid for updates to the use cases / architecture diagrams.
Options:
- Consider removing derived piv entirely
- Replace with derived ? (word reference to nist sp)
- Focus on the small f federation / assertion model, and plug and play authenticators associated with the enterprise user via enterprise access managers (enterprise idp / sts / etc)
from ficam-arch.
addressed during architecture update working sessions - closing
from ficam-arch.
Related Issues (20)
- Privileged Access (comment) HOT 1
- Derived PIV Lifecycle Support
- Add custom 404 HOT 1
- Update styles to USWDS 2.x HOT 1
- Perform automated and manual 508 checks HOT 1
- federation services HOT 1
- Content Feedback HOT 1
- Formatting Feedback HOT 1
- Editorial Feedback HOT 1
- Consolidated Comments HOT 4
- General Questions/Feedback HOT 3
- Formatting Feedback - FPKIMA HOT 1
- Editorial Feedback - FPKIMA HOT 1
- Content Feedback - FPKIMA HOT 4
- Comments on draft v3 HOT 1
- Content Feedback - DoD CIO HOT 2
- Add use case for onboarding applications and resources HOT 1
- Privileged Access Management HOT 3
- Roll Federation & Governance into ICAM practice areas HOT 1
- Standards & Policies missing NISTIRs of importance
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ficam-arch.