BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

8.3 Mixed-Multi-Tenant Facility

NIST PIV and digital identity SP 800-116 Rev. 1 against SP 800-116
All changes in this version
removed 8 PACS Use Cases part of 8

Title changed

Before · SP 800-116

Mixed-Multi-Tenant Facility

After · SP 800-116 Rev. 1

Mixed-Multi-Tenant Facility

Control changed

Before · SP 800-116

The mixed-multi-tenant facility use case is an example of a facility with a mix of PIV cardholders and non-PIV cardholders. Therefore, some tenants in this facility may not possess PIV Cards for authentication. It may be difficult if not impossible to develop one acceptable security policy for all the tenants. The Federal tenants in this facility should ensure they have leverage to implement necessary PIV authentication mechanisms for access to their space. The tenant agencies should designate their own “Controlled, Limited, Exclusion” areas and then evaluate if the facility’s PACS will accommodate their security needs. Each Federal government tenant should ensure an appropriate PIV authentication mechanism from Table 7-1 is implemented for its designated areas. If the facility’s PACS cannot accommodate agencies’ security needs, the tenant agencies should establish their own PACS. This may be considered an inner perimeter to the facility. In this case, the outer perimeter (i.e., access to the building) does not provide any authentication context. The individual agency should manage its own PACS server and user access. In many cases, the tenant agency will not have the authority to implement security measures independently; however, relationships in place should be used to negotiate security measures. In the event that it is not possible to establish individual PACS and the facility is evaluated at FSL III or above, the tenant should consider the risk involved with inadequate security and make future plans to improve security posture in accordance with the PIMM model in Section 9.

After · SP 800-116 Rev. 1

The mixed-multi-tenant facility use case is an example of a facility with a mix of PIV cardholders and non-PIV cardholders. Therefore, some tenants in this facility may not possess PIV Cards for authentication. It may be difficult if not impossible to develop one acceptable security policy for all the tenants. The Federal tenants in this facility should ensure they have leverage to implement necessary PIV authentication mechanisms for access to their space. The tenant agencies should designate their own “Controlled, Limited, Exclusion” areas and then evaluate if the facility’s PACS will accommodate their security needs. Each Federal government tenant should ensure an appropriate PIV authentication mechanism from Table 7-1 is implemented for its designated areas. If the facility’s PACS cannot accommodate agencies’ security needs, the tenant agencies should establish their own PACS. This may be considered an inner perimeter to the facility. In this case, the outer perimeter (i.e., access to the building) does not provide any authentication context. The individual agency should manage its own PACS server and user access. In many cases, the tenant agency will not have the authority to implement security measures independently; however, relationships in place should be used to negotiate security measures. In the event that it is not possible to establish individual PACS and the facility is evaluated at FSL III or above, the tenant should consider the risk involved with inadequate security and make future plans to improve security posture in accordance with the PIMM model in Section 9.