Skip to content
Federal Identity, Credential, and Access Management - Physical Access Control Systems (PACS)
JavaScript CSS HTML
Branch: staging
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_includes
_layouts
_sass
assets
img
pages
.codeinventory.yml
.gitignore
CONTRIBUTING.md
Gemfile
ISSUE_TEMPLATE.md
LICENSE.md
README.md
_config.yml

README.md

This work is in early Alpha stage and is led by the GSA FICAM Program, in coordination with the ICAM Subcommittee of the Federal CIO Council and members of the Secure Technology Alliance Access Control Council.

(Additional repositories are under development for community contributors to share ICAM implementation guides, code, reference implementations, and solutions.)

Federal Identity, Credential, and Access Management (FICAM) Physical Access Control Systems (PACS)

This repository is for the collaborative development of the implementation guidance for FICAM PACS. The content supports the creation and future versions of "Modernizing PACS Infrastructure," previously found in the FICAM Roadmap and Implementation Guidance v2.0, Section 7.

Collaboration Overview

  1. Federal agencies would like an updated Physical Access Control System (PACS) implementation guide to:
  • Replace the FICAM Roadmap’s “Modernize PACS Infrastructure” section, as part of its deprecation process
  • Understand enterprise physical access control systems
  • Align Facility Security Level (FSL) and authentication
  • Procure a physical access control systems
  • Identify recommended training
  1. The existing draft in this repository was submitted by the Access Control Council of the Secure Technology Alliance and used a white paper model.
  • It needs to become a digital Playbook.
  • It needs to incorporate standard operating procedures and lessons learned from federal agencies.

Required Actions

GSA, federal agencies, and industry contributors will collaboratively revise the Playbook draft to meet the above objectives. Guidelines for content revisions are:

  • Digital friendly navigation (logical structure) to help the user find information quickly
  • Content compliance with current government policies, standards, regulations, and practices
  • Unnecessary content is eliminated
  • Any subjective material is removed--all information shall be objective
  • Short sentences, bullets, and checklists are used
  • Mobile-friendly, updated graphics are used based on the FICAM Architecture or other government graphics
  • Pain language and active voice
  • Acronyms are removed where not needed
  • Referenced documents are verified and do not included deprecated policy, standards, or best practices

Expected Outcomes

  • A clear, cohesive, user-friendly Playbook that will give federal agencies the information needed to understand, manage, procure, and deploy an enterprise physical access control system that complies with government policies, standards, regulations, and practices.

  • Should be understandable by Program Managers and Engineers.

Milestones and Issues (Links)

Content Pages for Contributors (Link)

General Practices

This content is Vendor-neutral. Marketing materials for Commercial Products should not be submitted. If you would like to contribute a page or content which includes Commercial Products or specific references for development and engineering, please review the Commercial Product trademark or copyright guides from the Product Vendor and reference those guides in your Pull Request.

Plain Language

Contributors should consider the audience when submitting content. Plain language benefits a broad audience. Review your proposed content for use of acronyms and specialized jargon before submitting.

How to Contribute

For information on how to contribute to the site, review Contributing. The source repository exists ficam-pacs.

Direct changes and line edits to the content may be submitted through a Pull Request by clicking Edit this page (upper right-hand corner of each page). You do not need to install any software to submit content. You can use GitHub's in-browser editor to edit files and submit a Pull Request for your changes to be merged.

Public domain

This project is in the worldwide public domain.

This project is in the public domain within the United States. Copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a Pull Request, you are agreeing to comply with this waiver of copyright interest.

Special Thanks

This repository is based on GitHub Pages and Jekyll templates.

Special thanks to the teams at 18F, 18F Pages, and US Digital Services Playbooks for their open and transparent model, which benefits citizens, government, and technology.

You can’t perform that action at this time.