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.5 Multi-Tenant Campus

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

Multi-Tenant Campus

After · SP 800-116 Rev. 1

Multi-Tenant Campus

Control changed

Before · SP 800-116

The multi-tenant campus environment is similar to the single-tenant campus except that individual tenants will have their own security policies and the enforcement may be different. A tenant may benefit from the authentication mechanism(s) implemented at the outer perimeter; however, agencies may implement their own PACS within their space. In this case, if an agency were to benefit from other agencies’ PACS, its PACS should have communication links with other PACS on the campus. Once again, each individual tenant within a campus should designate its own “Controlled, Limited, Exclusion” areas and identify appropriate PIV authentication mechanism(s) required for access to its space (see Figure 7-1). The tenants can then determine if they can simply use the campus PACS application, if they should add security by implementing an additional PIV authentication mechanism, or if they should implement a stand-alone PACS. Each individual tenant should ensure that appropriate PIV authentication mechanism(s) from Figure 7-1 are implemented for its designated areas.

After · SP 800-116 Rev. 1

The multi-tenant campus environment is similar to the single-tenant campus except that individual tenants will have their own security policies and the enforcement may be different. A tenant may benefit from the authentication mechanism(s) implemented at the outer perimeter; however, agencies may implement their own PACS within their space. In this case, if an agency were to benefit from other agencies’ PACS, its PACS should have communication links with other PACS on the campus. Once again, each individual tenant within a campus should designate its own “Controlled, Limited, Exclusion” areas and identify appropriate PIV authentication mechanism(s) required for access to its space (see Figure 7-1). The tenants can then determine if they can simply use the campus PACS application, if they should add security by implementing an additional PIV authentication mechanism, or if they should implement a stand-alone PACS. Each individual tenant should ensure that appropriate PIV authentication mechanism(s) from Figure 7-1 are implemented for its designated areas.